From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] dell-laptop: Add back rfkill code
Date: Mon, 2 Dec 2013 14:57:07 +0000 [thread overview]
Message-ID: <20131202145707.GA9914@srcf.ucam.org> (raw)
In-Reply-To: <20131202121104.GA5687@redhat.com>
On Mon, Dec 02, 2013 at 01:11:05PM +0100, Stanislaw Gruszka wrote:
> This is basically a revert of:
>
> commit a6c2390cd6d2083d27a2359658e08f2d3df375ac
> Author: Matthew Garrett <mjg@redhat.com>
> Date: Fri Jun 1 12:46:56 2012 -0400
>
> dell-laptop: Remove rfkill code
>
> Except that patch add whilelist of Dell systems where dell-laptop
> specific RFKILL code is needed. For now, patch only add "Dell Latitude
> 6430U" laptop to whitelist, in the future other systems probably
> will be added.
It's already added back to 3.13, along with a whitelist entry for all
latitudes. I'm not going to add whitelisting for specific modules, and
I'm not enthusiastic about pushing to stable.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2013-12-02 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 12:11 [PATCH] dell-laptop: Add back rfkill code Stanislaw Gruszka
2013-12-02 14:57 ` Matthew Garrett [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=20131202145707.GA9914@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sgruszka@redhat.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