On Thu, Dec 13, 2012 at 12:37 AM, H. Peter Anvin <h...@zytor.com> wrote: > OK, so I'm not 100% sure how to best handle this patchset. I can carry it > in the x86 tree with the appropriate ACKs... which could lead to ugly merge > conflicts, or we can ask the respective driver authors to take their bits... > but that gives a sequencing problem (the core patchset depends on a bunch of > outside trees in order to be tested.) > > Either way it is a late pull for 3.8 at best... however, the risk seems low > so *maybe* that is acceptable.
I'd put the whole series into a separate branch by itself and any subsystems with problematic conflicts can merge it into their trees also. I'm fine with putting it in the x86 tree for v3.9. I don't think there is any huge rush on it. g. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
