From: Hans de Goede <hdegoede@redhat.com>
To: Fae <faenkhauser@gmail.com>, markgross@kernel.org
Cc: jorge.lopez2@hp.com, kai.heng.feng@canonical.com,
rishitbansal0@gmail.com, dhould3@gmail.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hp-wmi: add micmute to hp_wmi_keymap struct
Date: Tue, 25 Apr 2023 19:55:24 +0200 [thread overview]
Message-ID: <2225a78f-5766-c6d9-68d5-32da7f9d2791@redhat.com> (raw)
In-Reply-To: <20230425063644.11828-1-faenkhauser@gmail.com>
Hi,
On 4/25/23 08:36, Fae wrote:
> Fixes micmute key of HP Envy X360 ey0xxx
>
> Signed-off-by: Fae <faenkhauser@gmail.com>
Thank you for your patch, I've applied this patch to my review-hans
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Patches which are added to review-hans now are intended for
the next rc1. This branch will get rebased to the next rc1 when
it is out and after the rebasing the contents of review-hans
will be pushed to the platform-drivers-x86/for-next branch.
Regards,
Hans
> ---
> drivers/platform/x86/hp/hp-wmi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/platform/x86/hp/hp-wmi.c b/drivers/platform/x86/hp/hp-wmi.c
> index 873f59c3e280..6364ae262705 100644
> --- a/drivers/platform/x86/hp/hp-wmi.c
> +++ b/drivers/platform/x86/hp/hp-wmi.c
> @@ -211,6 +211,7 @@ struct bios_rfkill2_state {
> static const struct key_entry hp_wmi_keymap[] = {
> { KE_KEY, 0x02, { KEY_BRIGHTNESSUP } },
> { KE_KEY, 0x03, { KEY_BRIGHTNESSDOWN } },
> + { KE_KEY, 0x270, { KEY_MICMUTE } },
> { KE_KEY, 0x20e6, { KEY_PROG1 } },
> { KE_KEY, 0x20e8, { KEY_MEDIA } },
> { KE_KEY, 0x2142, { KEY_MEDIA } },
prev parent reply other threads:[~2023-04-25 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 6:36 Fae
2023-04-25 17:55 ` Hans de Goede [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=2225a78f-5766-c6d9-68d5-32da7f9d2791@redhat.com \
--to=hdegoede@redhat.com \
--cc=dhould3@gmail.com \
--cc=faenkhauser@gmail.com \
--cc=jorge.lopez2@hp.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rishitbansal0@gmail.com \
/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®