From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux x86 <x86@kernel.org>
Cc: David Woodhouse <dwmw@amazon.co.uk>,
Thomas Gleixner <tglx@linutronix.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Michael Kelley <mikelley@microsoft.com>,
Oleksandr Natalenko <oleksandr@natalenko.name>,
Helge Deller <deller@gmx.de>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Vincent Donnefort <vdonnefort@google.com>,
Bert Karwatzki <spasswolf@web.de>
Subject: Re: Fwd: kernel/cpu.c: linux misses the initialization of one CPU (off-by-one regression)
Date: Tue, 20 Jun 2023 14:36:21 +0200 [thread overview]
Message-ID: <90bf1d9d-1df3-acd1-5ecb-0c4e343ceffd@leemhuis.info> (raw)
In-Reply-To: <6a10ec48-3940-cd8d-5e34-b9ade9f87b82@gmail.com>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 29.05.23 03:50, Bagas Sanjaya wrote:
> I notice a regression report on Bugzilla [1]. Quoting from it:
> [...]
> #regzbot introduced: 18415f33e2ac4a https://bugzilla.kernel.org/show_bug.cgi?id=217498
> #regzbot title: Off-by-one CPU initalization when CONFIG_NR_CPUS equal to actual system CPU count
Fix in next (just like the culprit):
#regzbot fix: 06c6796e0304234
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-06-20 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 1:50 Bagas Sanjaya
2023-06-20 12:36 ` Linux regression tracking #update (Thorsten Leemhuis) [this message]
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=90bf1d9d-1df3-acd1-5ecb-0c4e343ceffd@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bagasdotme@gmail.com \
--cc=deller@gmx.de \
--cc=dwmw@amazon.co.uk \
--cc=gpiccoli@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=oleksandr@natalenko.name \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=spasswolf@web.de \
--cc=tglx@linutronix.de \
--cc=vdonnefort@google.com \
--cc=x86@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
all inboxes | Powered by JetHome®