From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Oleg Nesterov <oleg@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT PULL] siginfo fix for 4.16-rc1
Date: Wed, 31 Jan 2018 13:57:28 -0600 [thread overview]
Message-ID: <878tcdls2f.fsf@xmission.com> (raw)
In-Reply-To: <CA+55aFz+uhHRRDPHW_OU+MXmrpKdE3Eb=okczd5_0STaTDe8sQ@mail.gmail.com> (Linus Torvalds's message of "Wed, 31 Jan 2018 11:30:58 -0800")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Wed, Jan 31, 2018 at 8:19 AM, Eric W. Biederman
> <ebiederm@xmission.com> wrote:
>>
>> I had a brain fart when I received Stephen email about a compile failure
>> in linux-next. I thought the powerpc call to memory_failure had not
>> merged yet. Instead it simply failed to compile :(
>>
>> Linus can you please pull Stephen's fix so that powerpc builds correctly.
>
> I fixed this up in the merge already, afaik. Or is there some other failure?
My bad. I missed you fixed it in the merge.
I received a kbuild failure against linux-next this morning, and I
realized the build failure was against code that was already in 2.15 so
I should have patched and fixed that myself.
At which point I assumed the failure was because my siginfo code had
been merged into your tree.
Looking again you definitely fixed this in the merge. So I don't know
the story of the broken kbuild of linux-next. But I assume it will
sort itself out when the dust clears.
Apologies for the noise,
Eric
prev parent reply other threads:[~2018-01-31 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 20:02 [GIT PULL] siginfo cleanups for 4.16-rc1 Eric W. Biederman
2018-01-29 20:02 ` Eric W. Biederman
2018-01-30 2:36 ` Eric W. Biederman
2018-01-30 2:36 ` Eric W. Biederman
2018-01-31 16:19 ` [GIT PULL] siginfo fix " Eric W. Biederman
2018-01-31 16:19 ` Eric W. Biederman
2018-01-31 19:30 ` Linus Torvalds
2018-01-31 19:57 ` Eric W. Biederman [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=878tcdls2f.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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.