On Sat, Feb 4, 2017 at 8:21 AM, Michał Kępień <kernel@xxxxxxxxxx> wrote: >> 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@xxxxxxxxxx> 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. > > Thanks, guys, this is all helpful information. I have always assumed > testing was the correct base branch because my patches got pushed there > once they got accepted. Consider testing as a purgatory of the stuff. P.S. Darren fixed your name in previous patches and thus one more rebase happened in for-next. -- With Best Regards, Andy Shevchenko
