From: ayman.bagabas@gmail.com
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Hui Wang <hui.wang@canonical.com>,
Chris Chiu <chiu@endlessm.com>, Daniel Drake <drake@endlessm.com>,
Jian-Hong Pan <jian-hong@endlessm.com>,
Andy Shevchenko <andy@infradead.org>,
Darren Hart <dvhart@infradead.org>,
Jaroslav Kysela <perex@perex.cz>,
Kailang Yang <kailang@realtek.com>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v1 2/2] sound: Enable micmute led for Huawei laptops
Date: Wed, 15 May 2019 16:54:23 -0400 [thread overview]
Message-ID: <39f32949f84185c87b245b594131824b1865d1ee.camel@gmail.com> (raw)
In-Reply-To: <s5hk1erj20h.wl-tiwai@suse.de>
On Wed, 2019-05-15 at 15:11 +0200, Takashi Iwai wrote:
> On Mon, 13 May 2019 22:30:06 +0200,
> Ayman Bagabas wrote:
> > Since this LED is found on huawei laptops, we can hook it to
> > huawei-wmi platform driver which uses the common WMI interface
> > present
> > in these laptops to control the LED.
> >
> > I've also made some renames and used product name instead of common
> > name
> > to avoid confusion.
> >
> > Signed-off-by: Ayman Bagabas <ayman.bagabas@gmail.com>
>
> This looks applicable independently from the patch 1?
> If so, it can go via sound git tree while another via x86-platform
> tree.
>
Yes it is. Will send another one.
>
> thanks,
>
> Takashi
>
prev parent reply other threads:[~2019-05-15 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 20:30 [PATCH v1 0/2] Huawei WMI laptop extras driver Ayman Bagabas
2019-05-13 20:30 ` [PATCH v1 1/2] platform/x86: Huawei WMI laptop extras driver update Ayman Bagabas
2019-05-15 13:10 ` Takashi Iwai
2019-05-15 21:36 ` ayman.bagabas
2019-05-13 20:30 ` [PATCH v1 2/2] sound: Enable micmute led for Huawei laptops Ayman Bagabas
2019-05-15 13:11 ` Takashi Iwai
2019-05-15 20:54 ` ayman.bagabas [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=39f32949f84185c87b245b594131824b1865d1ee.camel@gmail.com \
--to=ayman.bagabas@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=andy@infradead.org \
--cc=chiu@endlessm.com \
--cc=drake@endlessm.com \
--cc=dvhart@infradead.org \
--cc=hui.wang@canonical.com \
--cc=jian-hong@endlessm.com \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).