public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: platform-driver-x86@vger.kernel.org,
	Ike Panhc <ike.pan@canonical.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ideapad-laptop: include Yoga 3 1170 in add rfkill whitelist
Date: Mon, 9 Nov 2015 13:46:46 -0800	[thread overview]
Message-ID: <20151109214646.GJ18221@malice.jf.intel.com> (raw)
In-Reply-To: <4760270.MzzySUYc0g@wuerfel>

On Fri, Nov 06, 2015 at 11:26:59PM +0100, Arnd Bergmann wrote:
> This changes the entry to the whitelist of machines that do not have
> a physical rfkill switch. Unfortunately, the Yoga 3 generation seems
> to use upper-case letters for the YOGA 3 Pro-1370, while it uses normal
> capitalization for its Yoga 3 1170 and 1470 siblings.
> 
> In order to catch all variants of the Yoga 3, I'm changing both
> the entry for the 1470 (using "Yoga" as the name) and the entry for
> the Pro 1370 (using all-caps "YOGA") to not match the exact model number
> but only the generation. This way, the 1170 and 1470 models share one
> entry, but if the firmware changes from one format to the other, it will
> still work.
> 
> The second entry for Yoga 2 Pro that was recently added for some
> reason ended up not being added in alphanumeric order, and I'm
> moving the Yoga 3 1470 entry down while making the change, so they
> are sorted more logically.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Queued to testing, thank you.

-- 
Darren Hart
Intel Open Source Technology Center

  reply	other threads:[~2015-11-09 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 21:28 [PATCH] ideapad-laptop: add support for Yoga 3 ESC key Arnd Bergmann
2015-11-06 22:26 ` [PATCH] ideapad-laptop: include Yoga 3 1170 in add rfkill whitelist Arnd Bergmann
2015-11-09 21:46   ` Darren Hart [this message]
2015-11-09 21:46 ` [PATCH] ideapad-laptop: add support for Yoga 3 ESC key Darren Hart

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=20151109214646.GJ18221@malice.jf.intel.com \
    --to=dvhart@infradead.org \
    --cc=arnd@arndb.de \
    --cc=ike.pan@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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