From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Corentin Chary <corentincj@iksaif.net>,
linux-acpi@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Julia Lawall <julia@diku.dk>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH 3/3] dell-laptop: fix rfkill memory leak on unload
Date: Mon, 14 Sep 2009 12:02:39 +0100 [thread overview]
Message-ID: <4AAE22CF.1020609@tuffmail.co.uk> (raw)
In-Reply-To: <20090914104616.GA6170@srcf.ucam.org>
Matthew Garrett wrote:
> On Mon, Sep 14, 2009 at 12:43:53PM +0200, Corentin Chary wrote:
>
>> rfkill_unregister() should always be followed by rfkill_destroy()
>>
>> Cc: Matthew Garrett <mjg@redhat.com>
>> Signed-off-by: Corentin Chary <corentincj@iksaif.net>
>>
>
> Acked-by: Matthew Garrett <mjg@redhat.com>
>
>
I can endorse this as I already submitted something similar :-).
<http://patchwork.kernel.org/patch/42699/> (with a disclaimer that it
was not tested on dell hardware).
next prev parent reply other threads:[~2009-09-14 11:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 10:43 [PATCH 0/3] rfkill_unregister() should always be followed by rfkill_destroy() Corentin Chary
2009-09-14 10:43 ` [PATCH 1/3] hp-wmi: fix rfkill memory leak on unload Corentin Chary
2009-09-14 10:43 ` [PATCH 2/3] thinkpad_acpi: " Corentin Chary
2009-09-14 10:43 ` [PATCH 3/3] dell-laptop: " Corentin Chary
2009-09-14 10:46 ` Matthew Garrett
2009-09-14 11:02 ` Alan Jenkins [this message]
2009-09-14 12:01 ` Corentin Chary
2009-09-14 13:22 ` [PATCH 2/3] thinkpad_acpi: " Henrique de Moraes Holschuh
2009-09-19 5:10 ` Len Brown
2009-09-14 10:59 ` [PATCH 1/3] hp-wmi: " Matthew Garrett
2009-09-19 5:13 ` Len Brown
2009-09-14 13:24 ` [PATCH 0/3] rfkill_unregister() should always be followed by rfkill_destroy() Henrique de Moraes Holschuh
2009-09-14 14:57 ` Alan Jenkins
2009-09-14 17:07 ` Henrique de Moraes Holschuh
2009-09-14 17:10 ` Henrique de Moraes Holschuh
2009-09-14 17:47 ` Corentin Chary
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=4AAE22CF.1020609@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=corentincj@iksaif.net \
--cc=johannes@sipsolutions.net \
--cc=julia@diku.dk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.