From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
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 0/3] rfkill_unregister() should always be followed by rfkill_destroy()
Date: Mon, 14 Sep 2009 15:57:15 +0100 [thread overview]
Message-ID: <4AAE59CB.8030702@tuffmail.co.uk> (raw)
In-Reply-To: <20090914132401.GC32253@khazad-dum.debian.net>
Henrique de Moraes Holschuh wrote:
> On Mon, 14 Sep 2009, Corentin Chary wrote:
>
>> drivers/platform/x86/dell-laptop.c | 36 ++++++++++++++++++++++-----------
>> drivers/platform/x86/hp-wmi.c | 2 +-
>> drivers/platform/x86/thinkpad_acpi.c | 1 +
>>
>
> These are also likely needed in 2.6.31, please add appropriate Cc: lines to
> stable@kernel.org while adding the Acked-By's.
>
>
Do they meet the -stable criteria?
...
- It must fix a real bug that bothers people (not a, "This could be a
problem..." type thing).
- It must fix a problem that causes a build error (but not for things
marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
security issue, or some "oh, that's not good" issue. In short, something
critical.
... (Documentation/stable_kernel_rules.txt)
Regards
Alan
next prev parent reply other threads:[~2009-09-14 14:57 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
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 [this message]
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=4AAE59CB.8030702@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=corentincj@iksaif.net \
--cc=hmh@hmh.eng.br \
--cc=johannes@sipsolutions.net \
--cc=julia@diku.dk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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