linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: PowerPC <linuxppc-dev@lists.ozlabs.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Sachin Sant <sachinp@linux.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/2] powerpc rng cleanups
Date: Wed, 27 Jul 2022 03:36:58 +0200	[thread overview]
Message-ID: <CAHmME9pMOQKnMUQQyOA+CkN5scQjtLN79pvdYSu70MkuU207cw@mail.gmail.com> (raw)
In-Reply-To: <YtVbbMpRbfCWEIFn@zx2c4.com>

Hi Michael,

On Mon, Jul 18, 2022 at 3:09 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hey again,
>
> On Tue, Jul 12, 2022 at 01:24:46AM +0200, Jason A. Donenfeld wrote:
> > These are two small cleanups for -next. This v5 rebases on the latest
> > git master, as some whitespace was added that made v4 no longer apply.
> >
> > Jason A. Donenfeld (2):
> >   powerpc/powernv: rename remaining rng powernv_ functions to pnv_
> >   powerpc/kvm: don't crash on missing rng, and use darn
> >
> >  arch/powerpc/include/asm/archrandom.h |  7 +--
> >  arch/powerpc/kvm/book3s_hv_builtin.c  |  7 +--
> >  arch/powerpc/platforms/powernv/rng.c  | 66 ++++++++++-----------------
> >  drivers/char/hw_random/powernv-rng.c  |  2 +-
> >  4 files changed, 30 insertions(+), 52 deletions(-)
>
> I think v5 has reached a completion point. Could you queue these up in
> some PPC tree for 5.20?

Just paging again. Do you think you could queue these up for 5.20?
This trivial series is over a month old now.

Thanks,
Jason

  reply	other threads:[~2022-07-27  1:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 23:24 [PATCH v5 0/2] powerpc rng cleanups Jason A. Donenfeld
2022-07-11 23:24 ` [PATCH v5 1/2] powerpc/powernv: rename remaining rng powernv_ functions to pnv_ Jason A. Donenfeld
2022-07-11 23:24 ` [PATCH v5 2/2] powerpc/kvm: don't crash on missing rng, and use darn Jason A. Donenfeld
2022-07-18 13:09 ` [PATCH v5 0/2] powerpc rng cleanups Jason A. Donenfeld
2022-07-27  1:36   ` Jason A. Donenfeld [this message]
2022-07-27  3:54     ` Michael Ellerman
2022-07-27 11:52       ` 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=CAHmME9pMOQKnMUQQyOA+CkN5scQjtLN79pvdYSu70MkuU207cw@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=sachinp@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).