From: "Luke Jones" <luke@ljones.dev>
To: "Hans de Goede" <hdegoede@redhat.com>,
"Benjamin Tissoires" <bentiss@kernel.org>
Cc: "Jiri Kosina" <jikos@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
corentin.chary@gmail.com, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v1 0/2] asus wmi and hid: use HID LED for brightness
Date: Fri, 07 Jun 2024 09:02:12 +1200 [thread overview]
Message-ID: <01808eec-29e4-4901-a5bf-396ec2eff3fe@app.fastmail.com> (raw)
In-Reply-To: <fc03506c-210f-4d79-9a99-8bc9b0587d25@redhat.com>
On Thu, 6 Jun 2024, at 9:53 PM, Hans de Goede wrote:
> Hi Benjamin,
>
> On 6/6/24 10:49 AM, Benjamin Tissoires wrote:
> > On May 29 2024, Hans de Goede wrote:
> >> Hi all,
> >>
> >> On 5/29/24 3:28 AM, Luke D. Jones wrote:
> >>> Changelog:
> >>> - v1
> >>> - Split the patch in two
> >>> - Move function body to asus-wmi and export
> >>> - Use array of names and for loops
> >>>
> >>> History:
> >>> - https://lore.kernel.org/linux-input/20240528013959.14661-1-luke@ljones.dev/T/#u
> >>>
> >>> Luke D. Jones (2):
> >>> hid-asus: use hid for brightness control on keyboard
> >>> hid-asus: change the report_id used for HID LED control
> >>>
> >>> drivers/hid/hid-asus.c | 32 +++++++++++++++++++-
> >>> drivers/platform/x86/asus-wmi.c | 35 +++++++++++++++++++++-
> >>> include/linux/platform_data/x86/asus-wmi.h | 10 +++++++
> >>> 3 files changed, 75 insertions(+), 2 deletions(-)
> >>
> >> Jiri, Benjamin since the first patch now also touches pdx86 files
> >> we need to coordinate merging this.
> >>
> >> There also is a long list of patches pending for
> >> drivers/platform/x86/asus-wmi.c
> >>
> >> So I would prefer to take this series (both patches) upstream through
> >> the pdx86 tree to avoid conflicts.
> >>
> >> May we have an ack from one of you for merging this through pdx86/for-next ?
> >
> > Sure:
> > Acked-by: Benjamin Tissoires <bentiss@kernel.org>
>
> Thank you for the ack.
>
> > But I haven't seen the v2. Are you sure you want to take this series as
> > it is?
>
> No I plan to wait for v2, I just thought it would be good to have
> an ack to merge this through the pdx86 tree beforehand.
My apologies for the delay, I have v2 prepped, but I'm waiting on feedback from a few folks regarding the 2024 G16 and G14, plus the TUF laptops - these are possibly affected by the patch. Shouldn't be more than a day or two now.
Regards,
Luke.
prev parent reply other threads:[~2024-06-06 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 1:28 Luke D. Jones
2024-05-29 1:28 ` [PATCH v1 1/2] hid-asus: use hid for brightness control on keyboard Luke D. Jones
2024-05-29 8:21 ` Hans de Goede
2024-05-29 1:28 ` [PATCH v1 2/2] hid-asus: change the report_id used for HID LED control Luke D. Jones
2024-05-29 8:25 ` Hans de Goede
2024-05-29 9:27 ` Luke Jones
2024-05-29 15:28 ` [PATCH v1 0/2] asus wmi and hid: use HID LED for brightness Hans de Goede
2024-06-06 8:49 ` Benjamin Tissoires
2024-06-06 9:53 ` Hans de Goede
2024-06-06 21:02 ` Luke Jones [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=01808eec-29e4-4901-a5bf-396ec2eff3fe@app.fastmail.com \
--to=luke@ljones.dev \
--cc=bentiss@kernel.org \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.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
all inboxes | Powered by JetHome®