linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	 Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org,
	 Linux-Arch <linux-arch@vger.kernel.org>,
	linux-alpha@vger.kernel.org,
	 Richard Henderson <richard.henderson@linaro.org>,
	 Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	 Matt Turner <mattst88@gmail.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	 "Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [GIT PULL] alpha: cleanups and build fixes for 6.10
Date: Fri, 31 May 2024 03:53:23 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2405310350360.23854@angie.orcam.me.uk> (raw)
In-Reply-To: <c585d63e73453082ecbf7ddc19d5116abdcfba79.camel@physik.fu-berlin.de>

On Mon, 13 May 2024, John Paul Adrian Glaubitz wrote:

> > Well, despite the discussion about timing of this, I have pulled this.
> > I still have a fond spot for alpha, even if it has the worst memory
> > ordering ever devised, but the lack of byte operations was an
> > inexcusable "we can deal with that in the compiler" senior moment in
> > the design. So good riddance.
> 
> As someone who spends a lot of personal time and energy and even money into
> Linux, I have to say the way this change was steamrolled into the kernel
> without any real discussion actually hurts.
> 
> It's days like these when I'm starting to question my efforts.

 FWIW, me too (the other factor being recurring PSU failures).  Sigh...

  Maciej

  reply	other threads:[~2024-05-31  2:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10 21:17 [GIT PULL] asm-generic cleanups for 6.10 Arnd Bergmann
2024-05-10 21:19 ` [GIT PULL] alpha: cleanups and build fixes " Arnd Bergmann
2024-05-10 21:40   ` John Paul Adrian Glaubitz
2024-05-10 22:28     ` Paul E. McKenney
2024-05-11 18:49       ` John Paul Adrian Glaubitz
2024-05-11 19:37         ` Paul E. McKenney
2024-05-11 20:08           ` Arnd Bergmann
2024-05-12  1:26             ` Paul E. McKenney
2024-05-12  6:02               ` John Paul Adrian Glaubitz
2024-05-12 14:44                 ` Paul E. McKenney
2024-05-13  3:50                   ` Akira Yokosawa
2024-05-13  4:03                     ` Paul E. McKenney
2024-05-13  6:28                       ` Arnd Bergmann
2024-05-13  9:26                     ` John Paul Adrian Glaubitz
2024-05-13 16:52                     ` Ulrich Teichert
2024-05-13 21:44                       ` John Paul Adrian Glaubitz
2024-05-13  7:10                   ` John Paul Adrian Glaubitz
2024-05-12  6:17   ` John Paul Adrian Glaubitz
2024-05-13 16:27   ` Linus Torvalds
2024-05-13 21:42     ` John Paul Adrian Glaubitz
2024-05-31  2:53       ` Maciej W. Rozycki [this message]
2024-05-13 17:05   ` pr-tracker-bot
2024-05-13 16:11 ` [GIT PULL] asm-generic cleanups " Linus Torvalds
2024-05-13 16:36   ` Arnd Bergmann
2024-05-20 22:35 ` pr-tracker-bot

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=alpine.DEB.2.21.2405310350360.23854@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=arnd@arndb.de \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).