| Message ID | 20220308215615.14183-1-arnd@kernel.org (mailing list archive) |
|---|---|
| Headers | show |
| Series | Kbuild: std=gnu11 changes | expand |
On Tue, Mar 8, 2022 at 1:56 PM Arnd Bergmann <arnd@kernel.org> wrote: > > From: Arnd Bergmann <arnd@arndb.de> > > I've incorporated the feedback from Masahiro Yamada in this > version, splitting out one more patch, rebasing on top of > the kbuild tree, and changing the order of the patches. > > Please apply to the kbuild tree. I'd actually like to see this as a separate branch, so that I can merge it early - or other peoples git branches end up depending on it. Yeah, it shouldn't change anything on its own, but since it allows for new syntax, we might have other things depending on it (I'm obviously thinking of the list_for_each_entry() series that keeps getting posted). Linus
On Wed, Mar 9, 2022 at 9:09 AM Linus Torvalds <torvalds@linux-foundation.org> wrote: > > On Tue, Mar 8, 2022 at 1:56 PM Arnd Bergmann <arnd@kernel.org> wrote: > > > > From: Arnd Bergmann <arnd@arndb.de> > > > > I've incorporated the feedback from Masahiro Yamada in this > > version, splitting out one more patch, rebasing on top of > > the kbuild tree, and changing the order of the patches. > > > > Please apply to the kbuild tree. > > I'd actually like to see this as a separate branch, so that I can > merge it early - or other peoples git branches end up depending on it. OK, I can apply this to a separate branch, kbuild-gnu11. (and I will queue this up shortly because it is already -rc7) Then, I will send two pull reqs in the next MW, but please note they will conflict with each other, between this gnu11 patch set and the following one in my usual kbuild branch: https://patchwork.kernel.org/project/linux-kbuild/patch/20220201213542.2808035-1-quic_eberman@quicinc.com/ I hope this is not a complex conflict, but please let me know if you have any requests to me. > Yeah, it shouldn't change anything on its own, but since it allows for > new syntax, we might have other things depending on it (I'm obviously > thinking of the list_for_each_entry() series that keeps getting > posted). > > Linus
On Wed, Mar 9, 2022 at 11:16 AM Masahiro Yamada <masahiroy@kernel.org> wrote: > > On Wed, Mar 9, 2022 at 9:09 AM Linus Torvalds > <torvalds@linux-foundation.org> wrote: > > > > On Tue, Mar 8, 2022 at 1:56 PM Arnd Bergmann <arnd@kernel.org> wrote: > > > > > > From: Arnd Bergmann <arnd@arndb.de> > > > > > > I've incorporated the feedback from Masahiro Yamada in this > > > version, splitting out one more patch, rebasing on top of > > > the kbuild tree, and changing the order of the patches. > > > > > > Please apply to the kbuild tree. > > > > I'd actually like to see this as a separate branch, so that I can > > merge it early - or other peoples git branches end up depending on it. > > > OK, I can apply this to a separate branch, kbuild-gnu11. > (and I will queue this up shortly because it is already -rc7) > > Then, I will send two pull reqs in the next MW, > but please note they will conflict with each other, > between this gnu11 patch set and the following > one in my usual kbuild branch: > > https://patchwork.kernel.org/project/linux-kbuild/patch/20220201213542.2808035-1-quic_eberman@quicinc.com/ > > > I hope this is not a complex conflict, but please let me know > if you have any requests to me. > > > > > All, applied to linux-kbuild/kbuild-gnu11. If somebody wants to give Reviewed-by, Acked-by, Tested-by, please. I will append them later.
On Wed, Mar 09, 2022 at 06:18:18PM +0900, Masahiro Yamada wrote: > On Wed, Mar 9, 2022 at 11:16 AM Masahiro Yamada <masahiroy@kernel.org> wrote: > > > > On Wed, Mar 9, 2022 at 9:09 AM Linus Torvalds > > <torvalds@linux-foundation.org> wrote: > > > > > > On Tue, Mar 8, 2022 at 1:56 PM Arnd Bergmann <arnd@kernel.org> wrote: > > > > > > > > From: Arnd Bergmann <arnd@arndb.de> > > > > > > > > I've incorporated the feedback from Masahiro Yamada in this > > > > version, splitting out one more patch, rebasing on top of > > > > the kbuild tree, and changing the order of the patches. > > > > > > > > Please apply to the kbuild tree. > > > > > > I'd actually like to see this as a separate branch, so that I can > > > merge it early - or other peoples git branches end up depending on it. > > > > > > OK, I can apply this to a separate branch, kbuild-gnu11. > > (and I will queue this up shortly because it is already -rc7) > > > > Then, I will send two pull reqs in the next MW, > > but please note they will conflict with each other, > > between this gnu11 patch set and the following > > one in my usual kbuild branch: > > > > https://patchwork.kernel.org/project/linux-kbuild/patch/20220201213542.2808035-1-quic_eberman@quicinc.com/ > > > > > > I hope this is not a complex conflict, but please let me know > > if you have any requests to me. > > > > > > > > > > > > > All, applied to linux-kbuild/kbuild-gnu11. > > If somebody wants to give Reviewed-by, Acked-by, Tested-by, please. > > I will append them later. For the series: Reviewed-by: Nathan Chancellor <nathan@kernel.org> Cheers, Nathan
On Thu, Mar 10, 2022 at 5:01 AM Nathan Chancellor <nathan@kernel.org> wrote: > > On Wed, Mar 09, 2022 at 06:18:18PM +0900, Masahiro Yamada wrote: > > On Wed, Mar 9, 2022 at 11:16 AM Masahiro Yamada <masahiroy@kernel.org> wrote: > > > > > > On Wed, Mar 9, 2022 at 9:09 AM Linus Torvalds > > > <torvalds@linux-foundation.org> wrote: > > > > > > > > On Tue, Mar 8, 2022 at 1:56 PM Arnd Bergmann <arnd@kernel.org> wrote: > > > > > > > > > > From: Arnd Bergmann <arnd@arndb.de> > > > > > > > > > > I've incorporated the feedback from Masahiro Yamada in this > > > > > version, splitting out one more patch, rebasing on top of > > > > > the kbuild tree, and changing the order of the patches. > > > > > > > > > > Please apply to the kbuild tree. > > > > > > > > I'd actually like to see this as a separate branch, so that I can > > > > merge it early - or other peoples git branches end up depending on it. > > > > > > > > > OK, I can apply this to a separate branch, kbuild-gnu11. > > > (and I will queue this up shortly because it is already -rc7) > > > > > > Then, I will send two pull reqs in the next MW, > > > but please note they will conflict with each other, > > > between this gnu11 patch set and the following > > > one in my usual kbuild branch: > > > > > > https://patchwork.kernel.org/project/linux-kbuild/patch/20220201213542.2808035-1-quic_eberman@quicinc.com/ > > > > > > > > > I hope this is not a complex conflict, but please let me know > > > if you have any requests to me. > > > > > > > > > > > > > > > > > > > > > All, applied to linux-kbuild/kbuild-gnu11. > > > > If somebody wants to give Reviewed-by, Acked-by, Tested-by, please. > > > > I will append them later. > > For the series: > > Reviewed-by: Nathan Chancellor <nathan@kernel.org> > For the series: Tested-by: Sedat Dilek <sedat.dilek@gmail.com> # LLVM/Clang v13.0.0 (x86-64) - Sedat -
From: Arnd Bergmann <arnd@arndb.de> I've incorporated the feedback from Masahiro Yamada in this version, splitting out one more patch, rebasing on top of the kbuild tree, and changing the order of the patches. Please apply to the kbuild tree. Arnd Cc: linux-kbuild@vger.kernel.org Cc: llvm@lists.linux.dev Arnd Bergmann (3): [v4] Kbuild: add -Wno-shift-negative-value where -Wextra is used [v4] Kbuild: move to -std=gnu11 Kbuild: use -std=gnu11 for KBUILD_USERCFLAGS Mark Rutland (1): [v4] Kbuild: use -Wdeclaration-after-statement Documentation/process/programming-language.rst | 6 +++--- .../translations/it_IT/process/programming-language.rst | 4 ++-- .../translations/zh_CN/process/programming-language.rst | 3 +-- .../translations/zh_TW/process/programming-language.rst | 3 +-- Makefile | 7 ++++--- arch/arm64/kernel/vdso32/Makefile | 3 ++- drivers/gpu/drm/i915/Makefile | 1 + drivers/staging/greybus/tools/Makefile | 3 ++- fs/btrfs/Makefile | 1 + scripts/Makefile.extrawarn | 1 + scripts/mod/modpost.c | 4 +++- 11 files changed, 21 insertions(+), 15 deletions(-)