From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Andres Salomon <dilinger@queued.net>,
"Timur I. Davletshin" <timur.davletshin@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux AMD GEODE <linux-geode@lists.infradead.org>
Subject: Re: Fwd: AMD Geode LX hardware RNG driver produces regular patterns (geode-rng.c)
Date: Tue, 26 Sep 2023 06:39:02 +0200 [thread overview]
Message-ID: <72d3eae0-efdc-41ad-bed9-008df36f320e@leemhuis.info> (raw)
In-Reply-To: <ZRIplFgg0ZnzGzre@debian.me>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 26.09.23 02:45, Bagas Sanjaya wrote:
> On Sun, Sep 10, 2023 at 03:54:28PM +0700, Bagas Sanjaya wrote:
>> On Thu, Sep 07, 2023 at 06:37:00PM +0700, Bagas Sanjaya wrote:
>>> #regzbot ^introduced: v4.14.267..v5.15.127
>>> #regzbot title: predictable urandom output on Alix 2d13
>>>
>>
>> #regzbot fix: https://lore.kernel.org/lkml/20230910083418.8990-1-jonas.gorski@gmail.com/
>>
>
> Fix up:
>
> #regzbot fix: hwrng: geode: fix accessing registers
Fix afaics was slightly renamed on merge, hence:
#regzbot fix: hwrng: geode - fix accessing registers
#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-09-26 4:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 11:37 Bagas Sanjaya
2023-09-10 8:54 ` Bagas Sanjaya
2023-09-26 0:45 ` Bagas Sanjaya
2023-09-26 4:39 ` 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=72d3eae0-efdc-41ad-bed9-008df36f320e@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bagasdotme@gmail.com \
--cc=dilinger@queued.net \
--cc=linux-geode@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=timur.davletshin@gmail.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
all inboxes | Powered by JetHome®