From: Greg KH <gregkh@suse.de>
To: Roland Vossen <rvossen@broadcom.com>
Cc: "devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] staging: brcm80211: bugfix for softmac crash on multi cpu configurations
Date: Tue, 25 Jan 2011 19:41:05 +0800 [thread overview]
Message-ID: <20110125114105.GA15568@suse.de> (raw)
In-Reply-To: <400C43189542CE41BC0A5B252FC90136952F08D15D@SJEXCHCCR02.corp.ad.broadcom.com>
On Tue, Jan 25, 2011 at 03:24:38AM -0800, Roland Vossen wrote:
> >Should this also go to the .37 stable kernel tree?
>
> Yes it should. Should I send you a patch for the .37 stable kernel tree ?
Not at the moment, I'll just mark it for the stable tree, and if it
doesn't apply there properly, I'll email you asking for an updated
version.
For more details about the stable kernel process, see the file,
Documentation/stable_kernel_rules.txt
thanks,
greg k-h
prev parent reply other threads:[~2011-01-25 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 10:51 [PATCH] staging: brcm80211: bugfix for softmac crash on multi cpu configurations Roland Vossen
2011-01-25 11:18 ` Greg KH
2011-01-25 11:24 ` Roland Vossen
2011-01-25 11:41 ` 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=20110125114105.GA15568@suse.de \
--to=gregkh@suse.de \
--cc=devel@linuxdriverproject.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rvossen@broadcom.com \
/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;
as well as URLs for NNTP newsgroup(s).