From: Greg KH <gregkh@linuxfoundation.org>
To: "ABRAHAM, KISHON VIJAY" <kishon@ti.com>
Cc: balbi@ti.com, linux-usb@vger.kernel.org, stable@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH RESEND] usb: musb: omap: fix crash when musb glue (omap) gets initialized
Date: Thu, 22 Mar 2012 15:34:11 -0700 [thread overview]
Message-ID: <20120322223411.GA32739@kroah.com> (raw)
In-Reply-To: <CAAe_U6J8hpGWAZPnfYOWuM=mVxW84cs=ajhdedBKx+pLXOSyhw@mail.gmail.com>
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@linuxfoundation.org> 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@linuxfoundation.org> 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-03-22 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 10:35 [PATCH RESEND] usb: musb: omap: fix crash when musb glue (omap) gets initialized Kishon Vijay Abraham I
2012-03-22 14:33 ` Greg KH
2012-03-22 21:34 ` ABRAHAM, KISHON VIJAY
2012-03-22 21:39 ` Greg KH
[not found] ` <20120322213918.GA11352-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-03-22 22:29 ` ABRAHAM, KISHON VIJAY
2012-03-22 22:34 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120322223411.GA32739@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@ti.com \
--cc=kishon@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox