[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210120134904.GA20315@willie-the-truck>
Date: Wed, 20 Jan 2021 13:49:04 +0000
From: Will Deacon <will@...nel.org>
To: Andre Przywara <andre.przywara@....com>
Cc: Marc Zyngier <maz@...nel.org>,
Russell King <linux@...linux.org.uk>,
Catalin Marinas <catalin.marinas@....com>,
Ard Biesheuvel <ardb@...nel.org>, kernel-team@...roid.com,
Theodore Ts'o <tytso@....edu>, Mark Brown <broonie@...nel.org>,
Sudeep Holla <sudeep.holla@....com>,
linux-kernel@...r.kernel.org,
Linus Walleij <linus.walleij@...aro.org>,
kvmarm@...ts.cs.columbia.edu,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v6 0/5] ARM: arm64: Add SMCCC TRNG entropy service
On Wed, Jan 20, 2021 at 01:45:24PM +0000, Andre Przywara wrote:
> On Wed, 20 Jan 2021 13:26:26 +0000
> Marc Zyngier <maz@...nel.org> wrote:
>
> Hi,
>
> > On 2021-01-20 13:01, Will Deacon wrote:
> > > On Wed, 6 Jan 2021 10:34:48 +0000, Andre Przywara wrote:
> > >> a fix to v5, now *really* fixing the wrong priority of SMCCC vs.
> > >> RNDR in arch_get_random_seed_long_early(). Apologies for messing
> > >> this up in v5 and thanks to broonie for being on the watch!
> > >>
> > >> Will, Catalin: it would be much appreciated if you could consider
> > >> taking
> > >> patch 1/5. This contains the common definitions, and is a
> > >> prerequisite for every other patch, although they are somewhat
> > >> independent and likely
> > >> will need to go through different subsystems.
> > >>
> > >> [...]
> > >
> > > Applied the first patch only to arm64 (for-next/rng), thanks!
> > >
> > > [1/5] firmware: smccc: Add SMCCC TRNG function call IDs
> > > https://git.kernel.org/arm64/c/67c6bb56b649
> >
> > I can't see how the rest of the patches can go via any other tree
> > if all the definitions are in the first one.
> >
> > Andre, can you explain what your plan is?
>
> Well, I don't really have a great solution for that, other than hoping
> that 1/5 makes it into Linus' master at some point.
>
> I see that it's a stretch, but pulling 1/5 into 5.11 now would
> prepare the stage for the others to go via any tree, into 5.12-rc1?
>
> Or you could maybe take both 1/5 and 5/5 into your kvm-arm tree, and
> would hope that a git rebase later would sort this out for you?
>
> But I think you are much more experienced in those kind of issues, so
> happy to hear about any other solutions.
for-next/rng is a stable branch, so anybody who wants the first patch can
just pull it (without anything I queue on top).
Will
Powered by blists - more mailing lists