[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170919080000.59a79ba2@canb.auug.org.au>
Date: Tue, 19 Sep 2017 08:00:10 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Pavel Machek <pavel@....cz>
Cc: Joonsoo Kim <iamjoonsoo.kim@....com>,
Tony Lindgren <tony@...mide.com>, pali.rohar@...il.com,
sre@...nel.org, kernel list <linux-kernel@...r.kernel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-omap@...r.kernel.org, khilman@...nel.org,
aaro.koskinen@....fi, ivo.g.dimitrov.75@...il.com,
patrikbachan@...il.com, serge@...lyn.com, abcloriens@...il.com,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
Vlastimil Babka <vbabka@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Russell King <linux@...linux.org.uk>
Subject: Re: Linux-next broken for 2 weeks was Re: n900 in next-20170901
Hi Pavel,
On Mon, 18 Sep 2017 10:11:09 +0200 Pavel Machek <pavel@....cz> wrote:
>
> Unfortunately, rest of the world can reproduce the error, and it means
> linux-next is useless for us.
>
> I'd expect you to drop the relevant tree from linux-next when the
> error was reported. Clearly, those patches are unsuitable for 4.15, as
> they are broken, so they should not be in linux-next.
Andrew has asked me to drop the patches from linux-next today and I
have done so.
--
Cheers,
Stephen Rothwell
Powered by blists - more mailing lists