From: Michael Buesch <mb@bu3sch.de>
To: Greg KH <greg@kroah.com>
Cc: stable@kernel.org, linux-wireless@vger.kernel.org,
John Linville <linville@tuxdriver.com>,
bcm43xx-dev@lists.berlios.de
Subject: Re: [stable] [PATCH stable] b43legacy: Fix possible NULL pointer dereference in DMA code
Date: Sun, 22 Jun 2008 19:23:24 +0200 [thread overview]
Message-ID: <200806221923.24856.mb@bu3sch.de> (raw)
In-Reply-To: <20080622165959.GA18163@kroah.com>
On Sunday 22 June 2008 18:59:59 Greg KH wrote:
> On Fri, Jun 20, 2008 at 11:46:12AM +0200, Michael Buesch wrote:
> > This fixes a possible NULL pointer dereference in an error path of the
> > DMA allocation error checking code.
> >
> > Signed-off-by: Michael Buesch <mb@bu3sch.de>
> >
> > ---
> >
> > This patch is not merged to an upstream tree, yet, but is sent to John.
>
> In the future, if you want patches to get automatically added to stable
> when they go into Linus's tree, just add:
> Cc: stable <stable@kernel.org>
>
> to the "Signed-off-by:" area and we will get notified of it at merge
> time, so you don't have to resend it after it gets applied.
Ok, however often enough it is not trivial to port patches from head to stable.
A bug introduced by a stable port isn't something we really want to risk, I
think. So I'd like to test all stable patches in their final state before they
get submitted to stable.
So for this trivial patch I could probably have used the CC magic, however.
--
Greetings Michael.
prev parent reply other threads:[~2008-06-22 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 9:46 [PATCH stable] b43legacy: Fix possible NULL pointer dereference in DMA code Michael Buesch
2008-06-22 16:59 ` [stable] " Greg KH
2008-06-22 17:23 ` Michael Buesch [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=200806221923.24856.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=greg@kroah.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).