public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	 Linus Torvalds <torvalds@linux-foundation.org>,
	linux-efi@vger.kernel.org,
	 Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kbuild@vger.kernel.org,  David Sterba <dsterba@suse.com>
Subject: Re: fms extension (Was: [PATCH] fs/pipe: stop duplicating union pipe_index declaration)
Date: Sat, 1 Nov 2025 14:10:42 +0100	[thread overview]
Message-ID: <20251101-bugsieren-gemocht-0e6115014a45@brauner> (raw)
In-Reply-To: <20251031013457.GA2650519@ax162>

On Thu, Oct 30, 2025 at 09:34:57PM -0400, Nathan Chancellor wrote:
> On Thu, Oct 30, 2025 at 09:16:02PM +0100, Christian Brauner wrote:
> > On Thu, Oct 30, 2025 at 10:29:18AM -0700, Nathan Chancellor wrote:
> > > There are several other places in the kernel that blow away
> > > KBUILD_CFLAGS like this that will need the same fix (I went off of
> > > searching for -std=gnu11, as that was needed in many places to fix GCC
> > > 15). It is possible that we might want to take the opportunity to unify
> > > these flags into something like KBUILD_DIALECT_CFLAGS but for now, I
> > > just bothered with adding the flags in the existing places.
> > 
> > That should hopefully do it. Can you update the shared branch with that
> > and then tell me when I can repull?
> 
> I have applied this as commit e066b73bd881 ("kbuild: Add
> '-fms-extensions' to areas with dedicated CFLAGS") in the
> kbuild-ms-extensions branch. I may solicit acks from architecture
> maintainers but I would like to make sure there are no other surprises
> before then.

I'd like a stable branch before -rc5, please.

  reply	other threads:[~2025-11-01 13:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251023082142.2104456-1-linux@rasmusvillemoes.dk>
     [not found] ` <20251029-redezeit-reitz-1fa3f3b4e171@brauner>
     [not found]   ` <20251029173828.GA1669504@ax162>
     [not found]     ` <20251029-wobei-rezept-bd53e76bb05b@brauner>
     [not found]       ` <CAHk-=wjGcos7LACF0J40x-Dwf4beOYj+mhptD+xcLte1RG91Ug@mail.gmail.com>
     [not found]         ` <20251030-zuruf-linken-d20795719609@brauner>
     [not found]           ` <20251029233057.GA3441561@ax162>
2025-10-30 13:23             ` fms extension (Was: [PATCH] fs/pipe: stop duplicating union pipe_index declaration) Christian Brauner
2025-10-30 13:38               ` Ard Biesheuvel
2025-10-30 17:29                 ` Nathan Chancellor
2025-10-30 20:16                   ` Christian Brauner
2025-10-31  1:34                     ` Nathan Chancellor
2025-11-01 13:10                       ` Christian Brauner [this message]
2025-11-01 16:38                         ` Nathan Chancellor
2025-11-06 22:09                           ` Christian Brauner
2025-11-06 23:20                             ` Nathan Chancellor

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=20251101-bugsieren-gemocht-0e6115014a45@brauner \
    --to=brauner@kernel.org \
    --cc=ardb@kernel.org \
    --cc=dsterba@suse.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=nathan@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox