From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Darren Hart <dvhart@infradead.org>
Cc: corentin.chary@gmail.com, acpi4asus-user@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v3] asus-nb-wmi: add wapf=4 quirk for ASUS X75VD
Date: Thu, 18 Feb 2016 08:00:58 +0200 [thread overview]
Message-ID: <1789149.FKtgJXZfQF@spock> (raw)
In-Reply-To: <20160218052345.GC18421@dvhart-mobl5.amr.corp.intel.com>
Thanks for your patience ;).
On середа, 17 лютого 2016 р. 21:23:45 EET Darren Hart wrote:
> On Wed, Feb 17, 2016 at 01:35:46PM +0200, Oleksandr Natalenko wrote:
> > Wi-Fi on ASUS X75VD laptop does not work unless asus_nb_wmi module
> > is loaded with wapf=4 option. Add quirk for this.
> >
> > Signed-off-by: Oleksandr Natalenko <oleksandr@natalenko.name>
>
> Queued to testing, thanks.
prev parent reply other threads:[~2016-02-18 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 11:35 [PATCH RESEND v3] asus-nb-wmi: add wapf=4 quirk for ASUS X75VD Oleksandr Natalenko
2016-02-18 5:23 ` Darren Hart
2016-02-18 6:00 ` Oleksandr Natalenko [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=1789149.FKtgJXZfQF@spock \
--to=oleksandr@natalenko.name \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=dvhart@infradead.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