Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1573550
| From | Darren Hart <dvhart@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 0/4] fujitsu_init() cleanup |
| Date | 2017-02-04 01:50 +0100 |
| Message-ID | <t6WIa-13a-11@gated-at.bofh.it> (permalink) |
| References | <sZ7U5-7f-3@gated-at.bofh.it> <sZ8ZQ-L2-21@gated-at.bofh.it> <sZ9VT-1kp-23@gated-at.bofh.it> <t6MIO-2yZ-21@gated-at.bofh.it> <t6MSt-2Co-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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@kempniu.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
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH 0/4] fujitsu_init() cleanup Michał Kępień <kernel@kempniu.pl> - 2017-02-03 15:10 +0100
Re: [PATCH 0/4] fujitsu_init() cleanup Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-02-03 15:20 +0100
Re: [PATCH 0/4] fujitsu_init() cleanup Darren Hart <dvhart@infradead.org> - 2017-02-04 01:50 +0100
Re: [PATCH 0/4] fujitsu_init() cleanup Michał Kępień <kernel@kempniu.pl> - 2017-02-04 07:30 +0100
Re: [PATCH 0/4] fujitsu_init() cleanup Andy Shevchenko <andy.shevchenko@gmail.com> - 2017-02-04 15:20 +0100
csiph-web