From: Borislav Petkov <bp@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
Kees Cook <keescook@chromium.org>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: linux-next: build failure after merge of the tip tree
Date: Mon, 30 Mar 2020 09:48:23 +0200 [thread overview]
Message-ID: <20200330074823.GA14624@zn.tnic> (raw)
In-Reply-To: <20200330150819.7f0199a2@canb.auug.org.au>
On Mon, Mar 30, 2020 at 03:08:19PM +1100, Stephen Rothwell wrote:
> What you really need is an Ack from the PowerPC people for the fix you
> suggested and then tha fix should go in the same series that is now
> causing the failure (preferably before the problematic (for PowerPC)
> patch.
I'll zap this commit from the tip lineup. There's always another merge
window.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
next prev parent reply other threads:[~2020-03-30 7:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200330143529.4dafeb34@canb.auug.org.au>
[not found] ` <CAMe9rOqnRCEdHhSHOT=Ut11D3O2WhjiFYhvPnaU5dANZNPE-=A@mail.gmail.com>
2020-03-30 4:08 ` linux-next: build failure after merge of the tip tree Stephen Rothwell
2020-03-30 7:48 ` Borislav Petkov [this message]
2020-03-30 8:04 ` Michael Ellerman
2020-03-30 8:16 ` Borislav Petkov
2020-03-30 11:34 ` H.J. Lu
2022-12-02 0:26 Stephen Rothwell
2022-12-02 1:33 ` Benjamin Gray
2022-12-02 9:37 ` Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2013-02-02 5:04 Stephen Rothwell
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=20200330074823.GA14624@zn.tnic \
--to=bp@suse.de \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).