From: Mousou Yuu <guogaishiwo@gmail.com>
To: "João Paulo Rechi Vita" <jprvita@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
Darren Hart <dvhart@infradead.org>,
Corentin Chary <corentin.chary@gmail.com>,
acpi4asus-user@lists.sourceforge.net
Subject: Re: [PATCH 1/1] asus-wireless: New driver for asus wireless button
Date: Sat, 19 Dec 2015 17:30:23 +0800 [thread overview]
Message-ID: <20151219173023.2fde2cf95a76aaf70779c1b2@gmail.com> (raw)
In-Reply-To: <CA+A7VXWtoy3sDqYNSXD0L5Yhvc5CrQ-=FXtGhSgcvY7wqPcx4A@mail.gmail.com>
On Sat, 19 Dec 2015 00:59:58 -0500
João Paulo Rechi Vita <jprvita@gmail.com> wrote:
> I have sent a patch series to this list to drive the exact same device
> your proposed module is driving, about 4 days ago. The first message
> in the thread is titled "[RFC 0/4] Asus Wireless Radio Control
> driver". Could you check if that works on your laptop as well? After a
> quick glance through your patch I think it will work just fine. My
> series also deals with the airplane mode LED, does your laptop has an
> LED as well? If so, can you check if the LED is being driven as
> expected? In one of the systems I have access to there is a conflict
> with asus-wmi (Asus re-used the previous WLAN LED id for this one) and
> the LED is inverted.
Oh, I should have searched the archive before submitting, it's the first
time I use mailing list...
I tested your patch on my U303LB model: there is no conflict, and airplane
hotkey works. But the patch has no effect on LED (still "inverted").
If I have to fix LED problem, I will consider modifying only asus-wmi and
asus-nb-wmi.
prev parent reply other threads:[~2015-12-19 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 1:34 [PATCH 1/1] asus-wireless: New driver for asus wireless button Mousou Yuu
2015-12-19 5:59 ` João Paulo Rechi Vita
2015-12-19 9:30 ` Mousou Yuu [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=20151219173023.2fde2cf95a76aaf70779c1b2@gmail.com \
--to=guogaishiwo@gmail.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=dvhart@infradead.org \
--cc=jprvita@gmail.com \
--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