mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: John Dahlstrom <jodarom@SDF.ORG>
Cc: Ike Panhc <ike.pan@canonical.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/1] ideapad-laptop: Add ideapad Y700 (15) to the no_hw_rfkill DMI list
Date: Mon, 29 Feb 2016 14:13:21 -0800	[thread overview]
Message-ID: <20160229221321.GC7499@dvhart-mobl5.amr.corp.intel.com> (raw)
In-Reply-To: <Pine.NEB.4.64.1602261748330.4769@norge.freeshell.org>

On Sat, Feb 27, 2016 at 12:49:03AM -0600, John Dahlstrom wrote:
> On Fri, 26 Feb 2016, Darren Hart wrote:
> >On Mon, Feb 22, 2016 at 10:29:48PM -0600, John Dahlstrom wrote:
> [...]
> >>Thank you for that information. One commit is sufficient to apply the patch
> >>to all kernel versions without fuzz:
> >>
> >>4fa9dab ideapad_laptop: Lenovo G50-30 fix rfkill reports wireless blocked
> >
> >This does not yield correct results for me on 3.17 (or 3.17.8). Do you get
> >different results from the following?
> >
> [...]
> >Note that the DMI match blocks were stuffed in the middle of the
> >ideapad_acpi_add() function instead of the no_hw_rfkill.
> 
> The v3, v4, and v5 patch submissions had been corrupted by spurious
> whitespace inserted by my email client. I have sent a corrected version,
> [PATCH v6 1/1] ideapad-laptop: Add ideapad Y700 (15) to the no_hw_rfkill DMI list
> 
> After submission, I verified the successful application of the patch
> as received by the mailing list.
> 
> I also ran git clone, "git checkout -b 3.17 v3.17", and
> "git cherry-pick 4fa9dab", followed by patch with success.

OK, I've replaced the one in for-next with this one.

I'm not keen on backporting only certain dmi match patches back to stable, but I
don't want to discourage people from working to get the hardware they care about
supported in stable either.

Thanks for sticking with it and seeing this through to completion.

-- 
Darren Hart
Intel Open Source Technology Center

      reply	other threads:[~2016-02-29 22:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20  1:34 John Dahlstrom
2016-02-22 22:14 ` Darren Hart
2016-02-23  4:29   ` John Dahlstrom
2016-02-26 18:56     ` Darren Hart
2016-02-27  6:49       ` John Dahlstrom
2016-02-29 22:13         ` Darren Hart [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=20160229221321.GC7499@dvhart-mobl5.amr.corp.intel.com \
    --to=dvhart@infradead.org \
    --cc=ike.pan@canonical.com \
    --cc=jodarom@SDF.ORG \
    --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

all inboxes | Powered by JetHome®