linux-alpha.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: paulmck@kernel.org, Arnd Bergmann <arnd@arndb.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	 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>
Subject: Re: [GIT PULL] alpha: cleanups and build fixes for 6.10
Date: Sun, 12 May 2024 08:02:59 +0200	[thread overview]
Message-ID: <975442500864e4f30a830afb4ffd09a9bedb65d6.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <f01d9eb2-9ab8-4e82-99d2-467385ebce2b@paulmck-laptop>

On Sat, 2024-05-11 at 18:26 -0700, Paul E. McKenney wrote:
> And that breaks things because it can clobber concurrent stores to
> other bytes in that enclosing machine word.

But pre-EV56 Alpha has always been like this. What makes it broken
all of a sudden?

My question was whether it actually stopped working, i.e. it's no
longer usable on these machines but that's not the case as far as
I know as not too long ago someone was actually running Debian on
a Jensen machine [1].

We could actually ask Ulrich Teichert what the current state is
on his Jensen machine.

Adrian

> [1] https://marc.info/?l=linux-alpha&m=163265555616841&w=2

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

  reply	other threads:[~2024-05-12  6:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <71feb004-82ef-4c7b-9e21-0264607e4b20@app.fastmail.com>
2024-05-10 21:19 ` [GIT PULL] alpha: cleanups and build fixes for 6.10 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 [this message]
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
2024-05-13 17:05   ` 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=975442500864e4f30a830afb4ffd09a9bedb65d6.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=arnd@arndb.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 read-only IMAP folder(s) and NNTP newsgroup(s).