linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Brivio <stefano.brivio@polimi.it>
To: Michael Buesch <mb@bu3sch.de>
Cc: John Linville <linville@tuxdriver.com>,
	bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43legacy: Fix rfkill allocation leakage in error paths
Date: Wed, 23 Jan 2008 13:55:09 +0100	[thread overview]
Message-ID: <20080123135509.539f645f@morte> (raw)
In-Reply-To: <200801231215.38768.mb@bu3sch.de>

On Wed, 23 Jan 2008 12:15:38 +0100
Michael Buesch <mb@bu3sch.de> wrote:

> We must kill rfkill in any error paths that trigger after rfkill init.
> 
> Signed-off-by: Michael Buesch <mb@bu3sch.de>

Acked-by: Stefano Brivio <stefano.brivio@polimi.it>


--
Ciao
Stefano

      reply	other threads:[~2008-01-23 13:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23 11:15 [PATCH] b43legacy: Fix rfkill allocation leakage in error paths Michael Buesch
2008-01-23 12:55 ` Stefano Brivio [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=20080123135509.539f645f@morte \
    --to=stefano.brivio@polimi.it \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    /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).