From: Greg KH <gregkh@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Sasha Levin <sashal@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: random.c backports for 5.18, 5.17, 5.15, and prior
Date: Fri, 27 May 2022 08:13:57 +0200 [thread overview]
Message-ID: <YpBsJRiZtCEH4hC8@kroah.com> (raw)
In-Reply-To: <CAHmME9oHuKcokorkRt9x264Be612Sh2iQrELveAzL1Yz6dhy5w@mail.gmail.com>
On Thu, May 26, 2022 at 05:15:12PM +0200, Jason A. Donenfeld wrote:
> Hi Greg,
>
> On Thu, May 26, 2022 at 4:44 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> > I get build errors in the 5.15 and 5.10 trees when applying these
> > patches.
> >
> > Here's the 5.10 error:
> > In file included from ../crypto/testmgr.c:32:
> > ../include/crypto/drbg.h:139:38: error: field 'random_ready' has incomplete type
> > 139 | struct random_ready_callback random_ready;
> > | ^~~~~~~~~~~~
> >
> >
> > And the same error in 5.15.
> >
> > So obviously I can't take them, I'm doing a simple 'make allmodconfig'
> > build for these trees on x86-64.
>
> Sorry about that. I've fixed the broken backport (of "random: replace
> custom notifier chain with standard one") and force pushed
> linux-5.10.y and linux-5.15.y branches.
All now queued up.
These are big changes overall, but as you've broken them up into the
original bits, they seem semi-sane. Let's see how the testing goes on
them...
thanks,
greg k-h
next prev parent reply other threads:[~2022-05-27 6:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 12:54 random.c backports for 5.18, 5.17, 5.15, and prior Jason A. Donenfeld
2022-05-23 13:36 ` Greg KH
2022-05-26 14:44 ` Greg KH
2022-05-26 15:15 ` Jason A. Donenfeld
2022-05-27 6:13 ` Greg KH [this message]
2022-05-30 8:11 ` Greg KH
2022-05-30 10:38 ` Jason A. Donenfeld
2022-06-10 9:05 ` Jason A. Donenfeld
2022-06-17 8:16 ` Greg KH
2022-05-24 12:04 ` Jason A. Donenfeld
2022-05-25 8:32 ` Jason A. Donenfeld
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=YpBsJRiZtCEH4hC8@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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