From: gregkh <gregkh@linuxfoundation•org>
To: Michael Ellerman <mpe@ellerman•id.au>
Cc: Arnd Bergmann <arnd@arndb•de>,
Olof's autobuilder <build@lixom•net>,
Olof Johansson <olof@lixom•net>,
kernel-build-reports@lists•linaro.org,
Oliver O'Halloran <oohall@gmail•com>,
linuxppc-dev@lists•ozlabs.org
Subject: Re: stable-rc build: 0 warnings 2 failures (stable-rc/v4.4.63-29-ge636782)
Date: Wed, 26 Apr 2017 10:30:55 +0200 [thread overview]
Message-ID: <20170426083055.GC13175@kroah.com> (raw)
In-Reply-To: <87r30f2270.fsf@concordia.ellerman.id.au>
On Wed, Apr 26, 2017 at 03:00:19PM +1000, Michael Ellerman wrote:
> Arnd Bergmann <arnd@arndb•de> writes:
>
> > On Tue, Apr 25, 2017 at 7:08 PM, Olof's autobuilder <build@lixom•net> wrote:
> >>
> >> Failed defconfigs:
> >> powerpc.pasemi_defconfig
> >> powerpc.ppc64_defconfig
> >>
> >> -------------------------------------------------------------------------------
> >>
> >> Errors:
> >>
> >> /work/build/batch/arch/powerpc/kernel/misc_64.S:72: Error: .localentry expression for `flush_icache_range' does not evaluate to a constant
> >
> > This is a regression in 4.4-stable-rc, caused by the backport of commit
> > 8f5f525d5b83f7d7 ("powerpc/64: Fix flush_(d|i)cache_range() called from
> > modules").
> >
> > The patch was also backported into v4.9-stable-rc, but did not cause
> > problems there. The fixes tag suggests that the patch is needed on
> > every version from 3.16 up, but apparently the fix needs to be a little
> > different compared to newer kernels.
>
> Yeah, the auto-backport failed, and then I sent a version for 4.4 which
> fixed the bug but broke other configs (big endian).
>
> I've asked Greg to drop it for now.
It's now dropped, thanks.
greg k-h
prev parent reply other threads:[~2017-04-26 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58ff8298.11c7620a.8183e.652d@mx.google.com>
2017-04-25 18:41 ` stable-rc build: 0 warnings 2 failures (stable-rc/v4.4.63-29-ge636782) Arnd Bergmann
2017-04-26 5:00 ` Michael Ellerman
2017-04-26 8:30 ` gregkh [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=20170426083055.GC13175@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=build@lixom$(echo .)net \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=olof@lixom$(echo .)net \
--cc=oohall@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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