From: Thomas Gleixner <tglx@linutronix.de>
To: "Linux regression tracking #update (Thorsten Leemhuis)"
<regressions@leemhuis.info>, Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>
Cc: Rick Edgecombe <rick.p.edgecombe@intel.com>,
Borislav Petkov <bp@alien8.de>
Subject: Re: Fwd: commit 9df9d2f0471b causes boot failure in pre-rc1 6.5 kernel
Date: Sat, 01 Jul 2023 20:13:59 +0200 [thread overview]
Message-ID: <878rbzxzx4.ffs@tglx> (raw)
In-Reply-To: <74014a7a-7d91-0854-8002-faf32d9c65e1@leemhuis.info>
On Sat, Jul 01 2023 at 14:43, Linux regression tracking #update (Thorsten Leemhuis) wrote:
> Bagas, FWIW, there was no need for this at all. Regzbot would have
> noticed that patch automatically due to the "Link:
> https://bugzilla.kernel.org/show_bug.cgi?id=217602" in the patch
> description (thx for this, tglx) once it landed in next or mainline
> (just like it noticed
> https://lore.kernel.org/lkml/168813193932.404.2885732890333911092.tip-bot2@tip-bot2/
> earlier).
I just looked at your tracking site and noticed a small hickup. There is
"Noteworthy: [1]" [1] is a link, but that does not really work:
https://bugzilla.kernel.org/show_bug.cgi?id=87jzvm12q0.ffs@tglx
Makes bugzilla unhappy :)
Thanks,
tglx
next prev parent reply other threads:[~2023-07-01 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 14:06 Fwd: commit 9df9d2f0471b causes boot failure in pre-rc1 6.5 kernel Bagas Sanjaya
2023-07-01 12:27 ` Bagas Sanjaya
2023-07-01 12:43 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-07-01 13:42 ` Bagas Sanjaya
2023-07-01 14:10 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-01 18:13 ` Thomas Gleixner [this message]
2023-07-02 12:12 ` Thorsten Leemhuis
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=878rbzxzx4.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=rick.p.edgecombe@intel.com \
/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