On Mon, Oct 14, 2013 at 09:09:14PM +0200, Sebastian Hesselbarth wrote: > On 10/14/2013 09:02 PM, Jason Cooper wrote: > >On Mon, Oct 14, 2013 at 08:43:49PM +0200, Sebastian Hesselbarth wrote: > >... > >>You know a good way to determine how far it should go back to -stable? > > > >$ git blame -L 338,338 drivers/pinctrl/mvebu/pinctrl-dove.c > >c9f95ced drivers/pinctrl/pinctrl-dove.c (Sebastian Hesselbarth > >2012-09-13 17:41:44 +0200 338) gcfg2 &= ~(DOVE_TWSI_ENABLE_OPTION2 | > >DOVE_TWSI_ENABLE_OPTION2); > > > >$ git tag --contains c9f95ced | grep '^v[23]\.[0-9][0-9]*' | sed -r -e > >'s/^(v[23]\.[0-9][0-9]*).*$/\1.x/' | sort -uV > >v3.7.x > >v3.8.x > >v3.9.x > >v3.10.x > >v3.11.x > >v3.12.x > > > >so it should get flagged for v3.7 and newer. > > > >Watch out for really old stuff, the regex above doesn't properly handle > >v2.6.XX.x... > > Ok, it is not in pre-v3.0, so the regex is fine. Thanks for the above - > and I also see git magic to resolve the rename of pinctrl-dove.c :)
rename occurred in 06763c7 pinctrl: mvebu: move to its own directory which was added to v3.8 > If it originates from before the rename, I guess we need two different > -stable patches, one for pre-rename, one for post-rename? No, the -stable maintainers handle that. If the patch is so complicated that you need separate patches for the different stable trees, that's a good indicator that it's not stable material. :-P thx, Jason. -- 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/
