On 22 February 2018 at 13:13, Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote: > > Not on your end. But thanks fo the reminder, and also for the hint > that you'd like it in -rc3. It's not likely to make -rc3 because I > like things to at least be in -next for a few days before I ask Linus > to pull them. > > But more importantly, what's the justification for adding this after > the merge window? It doesn't look like a regression or a fix for > something we broke in the merge window. It certainly *could* still be > merged for v4.16, but the default target would be v4.17. > > Bjorn Hi Bjorn Apologies, I thought all fixes got into the release candidates rather than just regressions I was hoping the original fix was going to make it into the merge window that just passed I just wanted to make sure the patch doesn't fall through the cracks I'm carrying this patch locally so it doesn't make too much difference to me which route it takes Thanks again Mike -- 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
