From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: Sergey Bronnikov <sergeyb@tarantool.org> Cc: Sergey Bronnikov <estetus@gmail.com>, max.kokryashkin@gmail.com, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 3/5][v3] cmake: introduce new targets Date: Wed, 9 Aug 2023 18:45:05 +0300 [thread overview] Message-ID: <ZNO0gTUMuqH7No73@root> (raw) In-Reply-To: <e1fcd295-df3c-0bc3-ced9-70e1223e0602@tarantool.org> Hi, Sergey! Thanks for the fixes! On 09.08.23, Sergey Bronnikov wrote: > Hi, Sergey! > > On 8/9/23 17:04, Sergey Kaplun wrote: <snipped> > >> include(LuaJITUtils) > >> include(SetBuildParallelLevel) > >> include(SetVersion) > >> +include(CheckPatch) > > And be included from test/CMakeLists.txt, not from root CMakeLists.txt. > Why? How checkpatch is related to testing? Not so much, but we still have `LuaJIT-luacheck` target in testing. I expected the same from `LuaJIT-checkpatch` target (and `test` target depends on `LuaJIT-checkpatch` target). But we may also move `LuaJIT-luacheck` in the separate include file in the separate patch series. > > <snipped> > >> + WORKING_DIRECTORY ${PROJECT_SOURCE_DIR} > > Also, we can't just check all patches with this since it will have > > TONS of errors. We must at least exclude all <src/*>, <dynasm/*> and > > include back files that are maintained by us. > > > > Without this, it becomes pointless, since we either > > * will have red always checkpatch job and don't be aware, so can miss > > some errors, either > > * will set ignore all (or something like it) to ignore all checkpatch > > warnings, including meaningful one. > > Agree, but this requires patching checkpatch itself, right now it is not > possible > > to suppress warnings for a certain files in patch. I'll try to implement > such patch. Looking forward to it! > <snipped> -- Best regards, Sergey Kaplun
next prev parent reply other threads:[~2023-08-09 15:50 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-02 8:52 [Tarantool-patches] [PATCH 0/5][v3] Fix typos and enable checkpatch Sergey Bronnikov via Tarantool-patches 2023-08-02 8:52 ` [Tarantool-patches] [PATCH 1/5][v3] ci: fix a step name Sergey Bronnikov via Tarantool-patches 2023-08-03 19:27 ` Maxim Kokryashkin via Tarantool-patches 2023-08-09 11:20 ` Sergey Kaplun via Tarantool-patches 2023-08-02 8:52 ` [Tarantool-patches] [PATCH 2/5][v3] codehealth: fix typos Sergey Bronnikov via Tarantool-patches 2023-08-03 19:29 ` Maxim Kokryashkin via Tarantool-patches 2023-08-09 12:58 ` Sergey Kaplun via Tarantool-patches 2023-08-09 14:41 ` Sergey Bronnikov via Tarantool-patches 2023-08-02 8:52 ` [Tarantool-patches] [PATCH 3/5][v3] cmake: introduce new targets Sergey Bronnikov via Tarantool-patches 2023-08-03 19:38 ` Maxim Kokryashkin via Tarantool-patches 2023-08-04 10:56 ` Sergey Bronnikov via Tarantool-patches 2023-08-09 14:04 ` Sergey Kaplun via Tarantool-patches 2023-08-09 14:55 ` Sergey Bronnikov via Tarantool-patches 2023-08-09 15:45 ` Sergey Kaplun via Tarantool-patches [this message] 2023-08-15 8:57 ` Maxim Kokryashkin via Tarantool-patches 2023-08-02 8:52 ` [Tarantool-patches] [PATCH 4/5][v3] ci: enable checkpatch Sergey Bronnikov via Tarantool-patches 2023-08-03 19:38 ` Maxim Kokryashkin via Tarantool-patches 2023-08-09 14:40 ` Sergey Kaplun via Tarantool-patches 2023-08-09 15:05 ` Sergey Bronnikov via Tarantool-patches 2023-08-14 9:22 ` Sergey Bronnikov via Tarantool-patches 2023-08-02 8:52 ` [Tarantool-patches] [PATCH 5/5][v3] test: fix codestyle Sergey Bronnikov via Tarantool-patches 2023-08-03 19:45 ` Maxim Kokryashkin via Tarantool-patches 2023-08-04 10:42 ` Sergey Bronnikov via Tarantool-patches 2023-08-09 14:07 ` Sergey Kaplun via Tarantool-patches
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=ZNO0gTUMuqH7No73@root \ --to=tarantool-patches@dev.tarantool.org \ --cc=estetus@gmail.com \ --cc=max.kokryashkin@gmail.com \ --cc=sergeyb@tarantool.org \ --cc=skaplun@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 3/5][v3] cmake: introduce new targets' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox