public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	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, 1 Jul 2023 20:42:30 +0700	[thread overview]
Message-ID: <e65bf45f-72c5-7239-6caa-609f3c9f24d2@gmail.com> (raw)
In-Reply-To: <74014a7a-7d91-0854-8002-faf32d9c65e1@leemhuis.info>

On 7/1/23 19:43, Linux regression tracking #update (Thorsten Leemhuis) wrote:
> On 01.07.23 14:27, Bagas Sanjaya wrote:
>> On Wed, Jun 28, 2023 at 09:06:22PM +0700, Bagas Sanjaya wrote:
>>> I notice a regression report on Bugzilla [1]. Quoting from it:
>> [....]
>>> See Bugzilla for the full thread.
>>>
>>> The reporter can't provide requested dmesg due to this is early
>>> boot failure, unfortunately.
>>>
>>> Nevertheless, this regression has already been taken care of on
>>> Bugzilla, but to ensure it is tracked and doesn't get fallen through
>>> cracks unnoticed, I'm adding it to regzbot:
>>>
>>> #regzbot introduced: 9df9d2f0471b https://bugzilla.kernel.org/show_bug.cgi?id=217602
>>> #regzbot title: early arch_cpu_finalize_init() cause immediate boot failure
>>
>> #regzbot fix: 0303c9729afc40
> 
> 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).
> 

OK, thanks for another tip! I was doing above because at the time
regzbot doesn't mark the regression as solved, so I had to manually
told it.

-- 
An old man doll... just what I always wanted! - Clara


  reply	other threads:[~2023-07-01 13:42 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 [this message]
2023-07-01 14:10       ` Linux regression tracking (Thorsten Leemhuis)
2023-07-01 18:13     ` Thomas Gleixner
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=e65bf45f-72c5-7239-6caa-609f3c9f24d2@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=rick.p.edgecombe@intel.com \
    --cc=tglx@linutronix.de \
    /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