On Fri, Mar 23, 2012 at 03:59:32AM +0530, ABRAHAM, KISHON VIJAY wrote: > Hi Greg, > > On Fri, Mar 23, 2012 at 3:09 AM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > On Fri, Mar 23, 2012 at 03:04:04AM +0530, ABRAHAM, KISHON VIJAY wrote: > >> Hi Greg, > >> > >> On Thu, Mar 22, 2012 at 8:03 PM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > >> > On Thu, Mar 22, 2012 at 04:05:45PM +0530, Kishon Vijay Abraham I wrote: > >> >> Upstream Commit: 7acc6197b76edd0b932a7cbcc6cfad0a8a87f026 > >> >> Upstream Kernel Tag: v2.6.38-rc5-94-g7acc619 > >> > > >> > <snip> > >> > > >> > <formletter> > >> > > >> > This is not the correct way to submit patches for inclusion in the > >> > stable kernel tree. Please read Documentation/stable_kernel_rules.txt > >> > for how to do this properly. > >> > > >> > </formletter> > >> > >> I really couldn't get what I'm missing after reading the > >> Documentation/stable_kernel_rules.txt :-( Can you kindly let me know > >> what I'm missing here? > > > > Read the version of that file in the 3.3 kernel release, it should > > explain what you are forgetting (hint, do you really want it applied to > > the 2.4 kernel tree?) > > I actually intended this patch to be back-ported to previous releases > which will have the issue. I'm not sure if it is right? And what releases are those? Hint, you need to tell us exactly what trees you want your patch applied to, otherwise we will just guess, and usually, incorrectly. Be specific. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
