linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antheas Kapenekakis <lkml@antheas.dev>
To: Jiri Kosina <jikos@kernel.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	platform-driver-x86@vger.kernel.org, linux-input@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	"Benjamin Tissoires" <bentiss@kernel.org>,
	"Corentin Chary" <corentin.chary@gmail.com>,
	"Luke D . Jones" <luke@ljones.dev>,
	"Hans de Goede" <hdegoede@redhat.com>
Subject: Re: [PATCH v5 09/11] HID: asus: add basic RGB support
Date: Sun, 30 Mar 2025 10:39:38 +0200	[thread overview]
Message-ID: <CAGwozwHbZHk_eSe-ZEM6jYM2HC4GxwnUrreZSh=+xJrKquEi9g@mail.gmail.com> (raw)
In-Reply-To: <26s13395-1ro2-37o8-01q5-6r4p09p69174@xreary.bet>

On Wed, 26 Mar 2025 at 12:00, Jiri Kosina <jikos@kernel.org> wrote:
>
> On Wed, 26 Mar 2025, Ilpo Järvinen wrote:
>
> > You don't need to "pause" for the merge window, in some subsystem
> > there's mandatory pause during merge window but I find that unnecessary.
> > I know people on pdx86 do review during merge window so no need to wait
> > when working with patches related to pdx86. Just don't expect patches
> > get applied during the merge window or right after it (the latter tends to
> > be the most busiest time of cycle for me) :-).
> >
> > It's more about the frequency, how often to send a series which is
> > relatively large. Large number of versions end up just filling inboxes
> > (and patchwork's pending patches list) and we don't have time to read them
> > all through so I suggest waiting like 3 days at minimum between versions
> > when the series is large or complex to give time to go through the series.
> >
> > This is not a hard rule, so if there are e.g. many significant changes,
> > feel free to "violate" it in that case.
>
> Exactly. I am unlikely to do much review during the merge window myself,
> but I'll pick up the patchset and followup once the merge window is over,
> so feel free to keep discussing and polishing it with me on CC :)
>
> Thanks,

I think we have reached a good point with this series. We can pick up
again when you guys are ready.

I will switch gears and look a bit into msi-wmi-platform for the MSI
Claw with Armin and we can revisit this come rc1.

Let's try to get through it early in 6.16 so that Luke can also do
what he wants to with the Ally, and let's push the oxpec move as well,
so I can get those two off my plate.

Antheas

> --
> Jiri Kosina
> SUSE Labs
>

  reply	other threads:[~2025-03-30  8:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 18:45 [PATCH v5 00/11] HID: asus: Add RGB Support to Asus Z13, Ally, unify backlight asus-wmi, and Z13 QOL Antheas Kapenekakis
2025-03-25 18:45 ` [PATCH v5 01/11] HID: asus: refactor init sequence per spec Antheas Kapenekakis
2025-03-25 18:45 ` [PATCH v5 02/11] HID: asus: prevent binding to all HID devices on ROG Antheas Kapenekakis
2025-03-25 18:45 ` [PATCH v5 03/11] HID: asus: add Z13 folio to generic group for multitouch to work Antheas Kapenekakis
2025-03-25 18:45 ` [PATCH v5 04/11] platform/x86: asus-wmi: Add support for multiple kbd RGB handlers Antheas Kapenekakis
2025-03-26 19:54   ` kernel test robot
2025-03-25 18:45 ` [PATCH v5 05/11] HID: asus: listen to the asus-wmi brightness device instead of creating one Antheas Kapenekakis
2025-03-25 18:45 ` [PATCH v5 06/11] platform/x86: asus-wmi: remove unused keyboard backlight quirk Antheas Kapenekakis
2025-03-25 18:45 ` [PATCH v5 07/11] platform/x86: asus-wmi: add keyboard brightness event handler Antheas Kapenekakis
2025-03-25 18:45 ` [PATCH v5 08/11] HID: asus: add support for the asus-wmi brightness handler Antheas Kapenekakis
2025-03-25 18:45 ` [PATCH v5 09/11] HID: asus: add basic RGB support Antheas Kapenekakis
2025-03-26  8:54   ` Ilpo Järvinen
2025-03-26  9:09     ` Antheas Kapenekakis
2025-03-26 10:24       ` Ilpo Järvinen
2025-03-26 11:00         ` Jiri Kosina
2025-03-30  8:39           ` Antheas Kapenekakis [this message]
2025-03-31  8:19             ` Luke D. Jones
2025-03-31  8:35               ` Antheas Kapenekakis
2025-03-25 18:45 ` [PATCH v5 10/11] HID: asus: add RGB support to the ROG Ally units Antheas Kapenekakis
2025-03-30 22:11   ` Luke D. Jones
2025-03-31  7:52     ` Antheas Kapenekakis
2025-04-10 19:39       ` Antheas Kapenekakis
2025-03-25 18:46 ` [PATCH v5 11/11] HID: asus: initialize LED endpoint early for old NKEY keyboards Antheas Kapenekakis

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='CAGwozwHbZHk_eSe-ZEM6jYM2HC4GxwnUrreZSh=+xJrKquEi9g@mail.gmail.com' \
    --to=lkml@antheas.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=luke@ljones.dev \
    --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;
as well as URLs for NNTP newsgroup(s).