All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Schier <nsc@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Nathan Chancellor <nathan@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	"Maciej W. Rozycki" <macro@orcam.me.uk>,
	Nick Huang <sef1548@gmail.com>,
	linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] scripts: headers_install.sh: Normalize __ASSEMBLY__ to __ASSEMBLER__
Date: Sat, 13 Jun 2026 12:13:53 +0200	[thread overview]
Message-ID: <ai0tYULNorM5UDqd@levanger> (raw)
In-Reply-To: <a31f2655-2ce8-4029-a63d-321c849730f7@t-8ch.de>

On Tue, Mar 24, 2026 at 08:58:08PM +0100, Thomas Weißschuh wrote:
> On 2026-03-24 11:35:01-0700, Nathan Chancellor wrote:
> > On Tue, Mar 24, 2026 at 06:05:34PM +0100, Thomas Weißschuh wrote:
> > > On 2026-03-13 16:56:18-0700, Nathan Chancellor wrote:
> > > > It sounds like the "< GCC 3.0" part of that might not be true based on
> > > > Maciej's research?
> > > > 
> > > >   https://lore.kernel.org/alpine.DEB.2.21.2603101412520.63708@angie.orcam.me.uk/
> > > 
> > > Yes, indeed. In my opinion the consistency aspect is still sufficient
> > > to have this change. What do you think?
> > 
> > Yes, I think so. Will you keep it as going from __ASSEMBLY__ to
> > __ASSEMBLER__? It probably makes more sense that way given there should
> > be no regressions on the compiler side and that is the intended end
> > result?
> 
> I would have stuck to the old name '__ASSEMBLY__', just for robustness
> and because we are late in the cycle.
> Then we can switch it early in the next cycle.

What's the state with this?  Shall this show up in linux-next early this
cycle?

-- 
Nicolas

  reply	other threads:[~2026-06-13 10:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 15:58 [PATCH] scripts: headers_install.sh: Normalize __ASSEMBLY__ to __ASSEMBLER__ Thomas Weißschuh
2026-03-13 23:56 ` Nathan Chancellor
2026-03-24 17:05   ` Thomas Weißschuh
2026-03-24 18:35     ` Nathan Chancellor
2026-03-24 19:58       ` Thomas Weißschuh
2026-06-13 10:13         ` Nicolas Schier [this message]
2026-06-13 16:57           ` 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=ai0tYULNorM5UDqd@levanger \
    --to=nsc@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=macro@orcam.me.uk \
    --cc=nathan@kernel.org \
    --cc=sef1548@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.