From: John Dahlstrom <jodarom@SDF.ORG>
To: Darren Hart <dvhart@infradead.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: Sat, 27 Feb 2016 00:49:03 -0600 (CST) [thread overview]
Message-ID: <Pine.NEB.4.64.1602261748330.4769@norge.freeshell.org> (raw)
In-Reply-To: <20160226185622.GA21870@dvhart-mobl5.amr.corp.intel.com>
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.
Kind regards,
John
next prev parent reply other threads:[~2016-02-27 6:50 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 [this message]
2016-02-29 22:13 ` 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=Pine.NEB.4.64.1602261748330.4769@norge.freeshell.org \
--to=jodarom@sdf.org \
--cc=dvhart@infradead.org \
--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
all inboxes | Powered by JetHome®