On Tue, 14 Jan 2014, Geert Uytterhoeven wrote: > > > I'm unsure about submitting this to -stable. I don't like the idea > > that the first debian user to boot a powerbook might see a crash > > (depending on bootloader etc). But not all stable trees carry df66834a > > which is a prerequisite. This patch is only applicable to 3.4.y and >= > > 3.9.y. Can you nominate particular stable trees? > > Sure, just add it to the comment, cfr. > Documentation/stable_kernel_rules.txt:
Yes. I read the docs before I wrote. > > - If the patch requires other patches as prerequisites which can be > cherry-picked than this can be specified in the following format in > the sign-off area: > > Cc: <[email protected]> # 3.3.x: a1f84a3: sched: Check for idle > Cc: <[email protected]> # 3.3.x: 1b9508f: sched: Rate-limit newidle > Cc: <[email protected]> # 3.3.x: fd21073: sched: Fix affinity logic > Cc: <[email protected]> # 3.3.x I didn't want the commit to be cherry-picked as it's already there (under different commit IDs) in some stable trees. The prerequisite commit is df66834a in mainline (merged in 3.10). It is known as f64747c9 in 3.9.y and 8cfd67a3 in 3.4.y. I only checked the trees in linux-stable.git which is not exhaustive but there are some stable trees that don't have it at all. Perhaps it would be best to request that the new patch only gets applied where the prerequisite patch was already in mainline, i.e. >= 3.10. Finn > > Gr{oetje,eeting}s, > > Geert > -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
