From: Michael Ellerman <mpe@ellerman•id.au>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
PowerPC <linuxppc-dev@lists•ozlabs.org>,
Andrew Morton <akpm@linux-foundation•org>
Subject: Re: linux-next: Tree for May 31
Date: Thu, 01 Jun 2017 17:03:33 +1000 [thread overview]
Message-ID: <87wp8w2nqy.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170601161315.6ec8e08e@canb.auug.org.au>
Stephen Rothwell <sfr@canb•auug.org.au> writes:
> Hi Michael,
>
> On Thu, 01 Jun 2017 16:07:51 +1000 Michael Ellerman <mpe@ellerman•id.au> wrote:
>>
>> Stephen Rothwell <sfr@canb•auug.org.au> writes:
>>
>> > Changes since 20170530:
>> >
>> > Non-merge commits (relative to Linus' tree): 3325
>> > 3598 files changed, 135000 insertions(+), 72065 deletions(-)
>>
>> More or less all my powerpc boxes failed to boot this.
>
> Good timing :-) How about the linux-next I just released. It has had
> a few of the mm changes removed since yesterday.
Yep, the offending patch seems to have been dropped.
cheers
next prev parent reply other threads:[~2017-06-01 7:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 5:32 linux-next: Tree for May 31 Stephen Rothwell
2017-06-01 6:07 ` Michael Ellerman
2017-06-01 6:13 ` Stephen Rothwell
2017-06-01 7:03 ` Michael Ellerman [this message]
2017-06-01 7:02 ` Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2024-05-31 5:41 Stephen Rothwell
2023-05-31 4:00 Stephen Rothwell
2022-05-31 4:54 Stephen Rothwell
2019-05-31 5:59 Stephen Rothwell
2018-05-31 9:40 Stephen Rothwell
2016-05-31 3:28 Stephen Rothwell
2013-05-31 5:08 Stephen Rothwell
2012-05-31 5:01 Stephen Rothwell
2011-05-31 4:49 Stephen Rothwell
2010-05-31 3:28 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=87wp8w2nqy.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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