On Mon, Jul 6, 2015 at 5:50 PM, Lee Jones <lee.jones@xxxxxxxxxx> wrote: > On Mon, 06 Jul 2015, Andy Shevchenko wrote: > >> On Mon, 2015-07-06 at 11:24 +0200, Geert Uytterhoeven wrote: >> > On Mon, Jul 6, 2015 at 11:10 AM, Andy Shevchenko >> > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: >> > > On Wed, 2015-06-24 at 12:31 +0100, Lee Jones wrote: >> > > > On Mon, 15 Jun 2015, Andy Shevchenko wrote: [] >> > > > Applied, thanks. >> > > >> > > Hmm… Seems kinda mistake. I can't see this applied (and required >> > > previous patches 4 and 5) to any of your branch neither in >> > > (today's) >> > > linux-next. >> > >> > New stuff applied after v4.1 couldn't show up in -next before v4.2 >> > -rc1 was >> > released (which just happened last night)? >> >> Might be, I would like to resend new version of my series and that's >> why I would like to have a branch to check what is already applied. So, >> if I can't see it does it mean it is brewed in the private repository? > > If you have patches that depend on this, they either need to come > through my tree, or you have to wait until the next kernel version > (which you probably don't want, right?). > > The alternative is that I unapply this patch and the whole lot can be > sucked up by the most appropriate subsystem. I resent a new version for other comments(still with all patches included). Meanwhile the patches 4-6 (from v4 or v5, where they are the same) could be applied in the first place. Can you clarify what exactly you have applied? The idea is to put the rest via your subsystem since it's most appropriate for this series. -- With Best Regards, Andy Shevchenko -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
