[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170204004425.GB38511@f23x64.localdomain>
Date: Sat, 4 Feb 2017 01:44:25 +0100
From: Darren Hart <dvhart@...radead.org>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Michał Kępień <kernel@...pniu.pl>,
Jonathan Woithe <jwoithe@...t42.net>,
Platform Driver <platform-driver-x86@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] fujitsu_init() cleanup
On Fri, Feb 03, 2017 at 04:13:40PM +0200, Andy Shevchenko wrote:
> On Fri, Feb 3, 2017 at 4:06 PM, Michał Kępień <kernel@...pniu.pl> wrote:
> > Darren, Andy,
> >
> > Please drop this patch series for now. I will send a rebased v2 after a
> > long overdue patch series from Alan Jenkins gets applied in a reworked
> > form.
>
> Noted.
>
> Just for you information. Our repo now consists three branches: fixes,
> for-next, and testing. testing is kinda for internal use, it might be
> broken or be in a wrong state.
> Better to use for-next as a base. For this cycle (which is my first as
In general, you should be able to use Linus' master as the base. Only if you
require patches already in for-next, should you use for-next.
--
Darren Hart
Intel Open Source Technology Center
Powered by blists - more mailing lists