On Mon, May 19, 2014 at 11:23:58PM +0300, Emmanuel Grumbach wrote: > > > On 05/19/2014 10:41 PM, Greg KH wrote: > > On Mon, May 19, 2014 at 01:40:34PM +0300, Emmanuel Grumbach wrote: > >> Hi, > >> > >> I need to disable a feature on 3.13 and 3.14. But I don't have any > >> patch upstream that I can point to as the patch that needs to be > >> backported. > >> We have a feature that is buggy in 3.13 and 3.14. We refactored (and > >> fixed) this feature in 3.15 but the refactor is really not stable > >> material, so basically, I can't backport the fix to 3.13 / 3.14. A > >> user reported that disabling the feature solved (part of) his issues: > >> https://bugzilla.kernel.org/show_bug.cgi?id=72601. > >> OTOH, I don't have any patch in linux.git that could be backported to > >> do what I want in 3.13 / 3.14 - i.e. disable the feature. > >> What is the right process here? I understand that this isn't covered > >> by the "stable rules". So what should I do here? > > > > Get the maintainer's approval to apply this patch and I can queue it up. > > Ok - thanks. It might be worthwhile to add this "exception path" in the Documentation :) No, it's such a rare exception, I don't want to "encourage" anyone to ever do it by documenting it. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html