From: "Luke Jones" <luke@ljones.dev>
To: "Jiri Kosina" <jikos@kernel.org>
Cc: "Benjamin Tissoires" <bentiss@kernel.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hid-asus: add ROG Ally X prod ID to quirk list
Date: Tue, 06 Aug 2024 11:49:49 +1200 [thread overview]
Message-ID: <e8a37c76-6922-459d-b4a2-688ee6287512@app.fastmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2408021251150.12664@cbobk.fhfr.pm>
On Fri, 2 Aug 2024, at 10:52 PM, Jiri Kosina wrote:
> On Thu, 25 Jul 2024, Luke D. Jones wrote:
>
> > The new ASUS ROG Ally X functions almost exactly the same as the previous
> > model, so we can use the same quirks.
> >
> > Signed-off-by: Luke D. Jones <luke@ljones.dev>
> > ---
> > drivers/hid/hid-asus.c | 3 +++
> > drivers/hid/hid-ids.h | 1 +
> > 2 files changed, 4 insertions(+)
> >
> > diff --git a/drivers/hid/hid-asus.c b/drivers/hid/hid-asus.c
> > index 9010f12a221e..e5f6664bac0f 100644
> > --- a/drivers/hid/hid-asus.c
> > +++ b/drivers/hid/hid-asus.c
> > @@ -1255,6 +1255,9 @@ static const struct hid_device_id asus_devices[] = {
> > { HID_USB_DEVICE(USB_VENDOR_ID_ASUSTEK,
> > USB_DEVICE_ID_ASUSTEK_ROG_NKEY_ALLY),
> > QUIRK_USE_KBD_BACKLIGHT | QUIRK_ROG_NKEY_KEYBOARD },
> > + { HID_USB_DEVICE(USB_VENDOR_ID_ASUSTEK,
> > + USB_DEVICE_ID_ASUSTEK_ROG_NKEY_ALLY_X),
> > + QUIRK_USE_KBD_BACKLIGHT | QUIRK_ROG_NKEY_KEYBOARD },
> > { HID_USB_DEVICE(USB_VENDOR_ID_ASUSTEK,
> > USB_DEVICE_ID_ASUSTEK_ROG_AZOTH_KEYBOARD),
> > QUIRK_USE_KBD_BACKLIGHT | QUIRK_ROG_NKEY_KEYBOARD },
> > diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
> > index fdf2d480533b..57f1f1bc5eb6 100644
> > --- a/drivers/hid/hid-ids.h
> > +++ b/drivers/hid/hid-ids.h
> > @@ -212,6 +212,7 @@
> > #define USB_DEVICE_ID_ASUSTEK_ROG_RAIKIRI_PAD 0x1abb
> > #define USB_DEVICE_ID_ASUSTEK_ROG_NKEY_ALLY 0x1abe
> > #define USB_DEVICE_ID_ASUSTEK_ROG_AZOTH_KEYBOARD 0x1a83
> > +#define USB_DEVICE_ID_ASUSTEK_ROG_NKEY_ALLY_X 0x1b4c
>
> I've applied the patch, but got a conflict here, because I don't see
> USB_DEVICE_ID_ASUSTEK_ROG_AZOTH_KEYBOARD in my tree, nor in Linus' tree.
> What tree was this patch generated against?
Apologies. I have a large tree of work for various asus devices. What you see should have been dropped but it looks like a git-rebase didn't go well.
Do you need me to regenerate it?
next prev parent reply other threads:[~2024-08-05 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 22:31 Luke D. Jones
2024-08-02 10:52 ` Jiri Kosina
2024-08-05 23:49 ` Luke Jones [this message]
2024-08-06 6:17 ` Jiri Kosina
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=e8a37c76-6922-459d-b4a2-688ee6287512@app.fastmail.com \
--to=luke@ljones.dev \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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®