stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	open list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Guenter Roeck <linux@roeck-us.net>, Shuah Khan <shuah@kernel.org>,
	patches@kernelci.org,
	Ben Hutchings <ben.hutchings@codethink.co.uk>,
	lkft-triage@lists.linaro.org,
	linux- stable <stable@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH 5.7 000/121] 5.7.13-rc2 review
Date: Wed, 5 Aug 2020 11:54:39 +0200	[thread overview]
Message-ID: <20200805095439.GB1634853@kroah.com> (raw)
In-Reply-To: <c32ad2216ca3dd83d6d3d740512db9de@kernel.org>

On Tue, Aug 04, 2020 at 10:23:06PM +0100, Marc Zyngier wrote:
> On 2020-08-04 19:33, Linus Torvalds wrote:
> > On Tue, Aug 4, 2020 at 1:21 AM Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > > 
> > > So Linus's tree is also broken here.
> > 
> > No, there's 835d1c3a9879 ("arm64: Drop unnecessary include from
> > asm/smp.h") upstream.
> 
> My bet is that Greg ended up with this patch backported to
> 5.7, but doesn't have 62a679cb2825 ("arm64: simplify ptrauth
> initialization") as the latter isn't a fix.
> 
> I don't think any of these two patches are worth backporting,
> to be honest.

I didn't have either of those patches, so I can try applying them to see
if the build errors go away.  But if you don't think they should be
applied, what should I do?

Here's what I did have queued up:

f227e3ec3b5c ("random32: update the net random state on interrupt and activity")
aa54ea903abb ("ARM: percpu.h: fix build error")
1c9df907da83 ("random: fix circular include dependency on arm64 after addition of percpu.h")
83bdc7275e62 ("random32: remove net_rand_state from the latent entropy gcc plugin")
c0842fbc1b18 ("random32: move the pseudo-random 32-bit definitions to prandom.h")

And that caused the builds to blow up.

So, what should I do here?

thanks,

greg k-h

  reply	other threads:[~2020-08-05  9:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  7:33 [PATCH 5.7 000/121] 5.7.13-rc2 review Greg Kroah-Hartman
2020-08-04  8:16 ` Naresh Kamboju
2020-08-04  8:21   ` Greg Kroah-Hartman
2020-08-04  9:00     ` Greg Kroah-Hartman
2020-08-04 18:33     ` Linus Torvalds
2020-08-04 21:23       ` Marc Zyngier
2020-08-05  9:54         ` Greg Kroah-Hartman [this message]
2020-08-05 11:19           ` Marc Zyngier
2020-08-05 13:20             ` Greg Kroah-Hartman
2020-08-05 16:51             ` Linus Torvalds
2020-08-04 16:49   ` Guenter Roeck

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=20200805095439.GB1634853@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=maz@kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=patches@kernelci.org \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).