From: Peter Xu <email@example.com>
To: Nick Bowler <firstname.lastname@example.org>
Cc: Linux regressions mailing list <email@example.com>,
Andrew Morton <firstname.lastname@example.org>
Subject: Re: PROBLEM: sparc64 random crashes starting w/ Linux 6.1 (regression)
Date: Thu, 16 Feb 2023 10:33:50 -0500 [thread overview]
Message-ID: <Y+5M3qezT2t0wPx+@x1n> (raw)
On Thu, Feb 16, 2023 at 12:32:54AM -0500, Nick Bowler wrote:
> On 2023-02-15, Peter Xu <email@example.com> wrote:
> > On Wed, Feb 15, 2023 at 03:49:56PM +0100, Linux regression tracking
> > (Thorsten Leemhuis) wrote:
> >> On 31.01.23 02:46, Nick Bowler wrote:
> >> > I'll keep running this for a while to see if any other problems come
> >> > up.
> >> Nick, I assume no other problems showed up?
> >> In that case Peter could send the patch in for merging. Or did you do
> >> that already?
> > Thanks for raising this again. Nop, I'm just waiting for a final ack from
> > Nick to make sure that nothing went wrong after the longer run.
> Oh, yes, it wasn't so much a "run" as just continuing to use the
> computer normally.
> Everything seems stable enough.
I've just posted a formal patch with you copied. There's a slight tweak
due to rebasing to the latest akpm tree, but I still attached your
tested-by for appreciations on the help, and I assume it should have the
same functional change.
next prev parent reply other threads:[~2023-02-16 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 2:17 PROBLEM: sparc64 random crashes starting w/ Linux 6.1 (regression) Nick Bowler
2023-01-29 22:14 ` Peter Xu
2023-01-30 1:36 ` Nick Bowler
2023-01-31 1:46 ` Nick Bowler
2023-02-15 14:49 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-15 15:21 ` Peter Xu
2023-02-16 5:32 ` Nick Bowler
2023-02-16 15:33 ` Peter Xu [this message]
2023-01-30 9:37 ` Linux kernel regression tracking (#adding)
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).