From: Matthew Wilcox <willy@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Erhard Furtner <erhard_f@mailbox.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux PowerPC <linuxppc-dev@lists.ozlabs.org>,
Mike Rapoport <rppt@kernel.org>
Subject: Re: [Bisected] PowerMac G5 fails booting kernel 6.6-rc3 (BUG: Unable to handle kernel data access at 0xfeffbb62ffec65fe)
Date: Fri, 6 Oct 2023 02:19:13 +0100 [thread overview]
Message-ID: <ZR9gkZKafUSNOAEf@casper.infradead.org> (raw)
In-Reply-To: <ZR9esG8H17LY2KOX@debian.me>
On Fri, Oct 06, 2023 at 08:11:12AM +0700, Bagas Sanjaya wrote:
> Matthew Wilcox, did you miss this regression report? You should look into it
> since it is (apparently) cause by a commit of yours.
No, I didn't miss it. I'm simply choosing to work on other things.
All this regression tracking nonsense and being told to work on things
by people who've appointed themselves my manager has completely sapped
my motivation to work on bugs. If you want me to work on things, *don't*
harass me.
next prev parent reply other threads:[~2023-10-06 1:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 11:27 [Bisected] PowerMac G5 fails booting kernel 6.6-rc3 (BUG: Unable to handle kernel data access at 0xfeffbb62ffec65fe) Erhard Furtner
2023-09-29 12:34 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-06 1:11 ` Bagas Sanjaya
2023-10-06 1:19 ` Matthew Wilcox [this message]
2023-10-06 6:57 ` Bagas Sanjaya
2023-10-06 5:34 ` Aneesh Kumar K.V
2023-10-06 10:45 ` Erhard Furtner
2023-10-06 12:08 ` Aneesh Kumar K.V
2023-10-06 14:12 ` Erhard Furtner
2023-10-11 23:47 ` Michael Ellerman
2023-10-12 14:20 ` Erhard Furtner
2023-10-12 11:41 ` Michael Ellerman
2023-10-12 14:49 ` Erhard Furtner
2023-10-17 3:40 ` Michael Ellerman
2023-10-17 23:01 ` Erhard Furtner
2023-10-18 5:45 ` Michael Ellerman
2023-10-18 10:34 ` Erhard Furtner
2025-04-08 5:55 ` Christophe Leroy
2025-04-11 9:24 ` Erhard Furtner
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=ZR9gkZKafUSNOAEf@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=erhard_f@mailbox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=regressions@lists.linux.dev \
--cc=rppt@kernel.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;
as well as URLs for NNTP newsgroup(s).