From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, stable@vger.kernel.org
Subject: Re: Build failure in v4.4.y.queue (ppc:allmodconfig)
Date: Thu, 9 May 2019 08:53:24 +0200 [thread overview]
Message-ID: <20190509065324.GA3864@kroah.com> (raw)
In-Reply-To: <20190508202642.GA28212@roeck-us.net>
On Wed, May 08, 2019 at 01:26:42PM -0700, Guenter Roeck wrote:
> I see multiple instances of:
>
> arch/powerpc/kernel/exceptions-64s.S:839: Error:
> attempt to move .org backwards
>
> in v4.4.y.queue (v4.4.179-143-gc4db218e9451).
>
> This is due to commit 9b2d4e06d7f1 ("powerpc/64s: Add support for a store
> forwarding barrier at kernel entry/exit"), which is part of a large patch
> series and can not easily be reverted.
>
> Guess I'll stop doing ppc:allmodconfig builds in v4.4.y ?
Michael, I thought this patch series was supposed to fix ppc issues, not
add to them :)
Any ideas on what to do here?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: stable@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: Build failure in v4.4.y.queue (ppc:allmodconfig)
Date: Thu, 9 May 2019 08:53:24 +0200 [thread overview]
Message-ID: <20190509065324.GA3864@kroah.com> (raw)
In-Reply-To: <20190508202642.GA28212@roeck-us.net>
On Wed, May 08, 2019 at 01:26:42PM -0700, Guenter Roeck wrote:
> I see multiple instances of:
>
> arch/powerpc/kernel/exceptions-64s.S:839: Error:
> attempt to move .org backwards
>
> in v4.4.y.queue (v4.4.179-143-gc4db218e9451).
>
> This is due to commit 9b2d4e06d7f1 ("powerpc/64s: Add support for a store
> forwarding barrier at kernel entry/exit"), which is part of a large patch
> series and can not easily be reverted.
>
> Guess I'll stop doing ppc:allmodconfig builds in v4.4.y ?
Michael, I thought this patch series was supposed to fix ppc issues, not
add to them :)
Any ideas on what to do here?
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-09 6:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 20:26 Build failure in v4.4.y.queue (ppc:allmodconfig) Guenter Roeck
2019-05-08 20:26 ` Guenter Roeck
2019-05-09 6:53 ` Greg Kroah-Hartman [this message]
2019-05-09 6:53 ` Greg Kroah-Hartman
2019-05-09 9:49 ` Michal Suchánek
2019-05-09 9:49 ` Michal Suchánek
2019-05-09 13:07 ` Guenter Roeck
2019-05-09 13:07 ` Guenter Roeck
2019-05-09 13:26 ` Michal Suchánek
2019-05-09 14:06 ` Guenter Roeck
2019-05-09 14:35 ` Michal Suchánek
2019-05-09 14:31 ` Michael Ellerman
2019-05-09 14:31 ` Michael Ellerman
2019-05-09 16:23 ` Guenter Roeck
2019-05-09 16:23 ` Guenter Roeck
2019-05-14 7:15 ` Michael Ellerman
2019-05-14 7:15 ` Michael Ellerman
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=20190509065324.GA3864@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.