mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: paulmck@kernel.org
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	 kernel-team@meta.com, Bradley Morgan <brads@mainlining.org>,
	Arnd Bergmann <arnd@kernel.org>,
	phoronix@phoronix.com
Subject: Re: [GIT PULL] Add two-byte cmpxchg emulation function for v7.4
Date: Wed, 21 Oct 2026 11:13:03 +0200	[thread overview]
Message-ID: <a0097437824f2ea0b94593770f13e14e92043507.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <851e3a8d-dd0d-49cb-8672-5cebc03d910b@paulmck-laptop>

Hello Paul,

On Tue, 2026-10-20 at 12:14 -0700, Paul E. McKenney wrote:
> On Tue, Oct 20, 2026 at 08:48:32PM +0200, John Paul Adrian Glaubitz wrote:
> > Hi Paul,
> > 
> > On Fri, 2026-10-16 at 20:51 -0700, Paul E. McKenney wrote:
> > > However, it sadly does not permit easy implementation of all algorithms
> > > needing on two-byte atomic operations because there are some systems still
> > > supported by Linux that do not have native two-byte store instructions.
> > > There is reason to believe that these systems will soon no longer be
> > > supported by Linux.
> > 
> > Since this paragraph has produced a headline today [1], would you mind
> > clarifying what you meant here? What architectures are you talking about?
> 
> The important word in the second paragraph quoted by the article is
> "systems", which is not "architectures".   To its credit, the article
> keeps this straight, but not so much the comments.
> 
> And here is Arnd Bergmann's patch that started this:
> 
> https://lore.kernel.org/all/20260908152808.3928630-4-arnd@kernel.org/
> 
> The system Arnd calls out is the Acorn Risc PC, which is one member of the
> Arm family.  So not an entire architecture, but rather just a particular
> implementation of an architecture, and an old one at that.  Not only
> that, but if I remember correctly, Arnd got considerable pushback,
> so I am not sure that his support-removal patch is going in just yet,
> as in I do not yet see it in -next.
> 
> Please feel free to add this as a comment to the article, as the site
> is not permitting me to do so.  I have added their feedback email on
> CC in case that helps, and in the hope that my doing so does not unduly
> annoy them.

Thanks a lot for the clarification, much appreciated!

Relieved,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2026-10-21  9:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17  3:51 Paul E. McKenney
2026-10-20 18:48 ` John Paul Adrian Glaubitz
2026-10-20 18:54   ` Bradley Morgan
2026-10-20 19:21     ` Paul E. McKenney
2026-10-20 19:26       ` Bradley Morgan
2026-10-20 19:14   ` Paul E. McKenney
2026-10-21  9:13     ` John Paul Adrian Glaubitz [this message]
2026-10-21  1:08 ` pr-tracker-bot
2026-10-23 11:26 ` Jan Engelhardt
2026-10-23 16:12   ` Paul E. McKenney
2026-11-02 12:21     ` Jan Engelhardt
2026-11-02 16:34       ` David Laight
2026-11-03  2:03         ` Jan Engelhardt

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=a0097437824f2ea0b94593770f13e14e92043507.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=arnd@kernel.org \
    --cc=brads@mainlining.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=phoronix@phoronix.com \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®