Am 23.10.2017 um 18:48 schrieb Michael Lyle: > On 10/23/2017 07:26 AM, Stefan Priebe - Profihost AG wrote: >> It seems i'm missing a5f3d8a5eaaf but i have 09b3efec81de. >> >> I missed it because >> git log ..linux-block/for-next -- drivers/md/bcache/ >> >> does not show it. It seems linux-block/for-next does not contain it? >> Which branch should i use? > > This is one of the pitfalls of selectively taking a bunch of changes > back into an older kernel series, especially from development trees. > linux-block/for-next is guaranteed to contain all the changes needed to > take the linux-next tree into complete state, but not necessarily to be > based on a point in time on linux-next that captures all past changes. > Similarly, there's no guarantee that current bcache code will work well > on the 4.4 kernel without changes-- i.e. I am accepting changes that > rely on recent changes in kernel facilities to compile, and I would > accept changes that rely on recent changes in semantics to be correct. Yes sure but that's no problem. I already backported them. Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
