From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "José Guilherme de Castro Rodrigues" <jose.guilherme.cr.bh@gmail.com>
Cc: Corentin Chary <corentin.chary@gmail.com>,
"Luke D. Jones" <luke@ljones.dev>,
Denis Benato <benato.denis96@gmail.com>,
Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: asus-wmi: fix camera key led on Zenbook S14
Date: Thu, 23 Apr 2026 14:29:32 +0300 (EEST) [thread overview]
Message-ID: <88b55672-8cdb-7aa9-634b-da8d59d03bf7@linux.intel.com> (raw)
In-Reply-To: <aelV0GZ8n5s9lXOf@djouze-zen>
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
On Wed, 22 Apr 2026, José Guilherme de Castro Rodrigues wrote:
> On Thu, Apr 09, 2026 at 03:45:29PM +0300, Ilpo Järvinen wrote:
> >
> > Please just send a new version. It will be much easier for me when I don't
> > need to hunt down odd spaces or do multi-line code edits.
>
> Sure, I sent the PATCH v2 a few days ago. I look forward for any
> feedback. Here is the link in case something went wrong and it did not
> arrive correctly, or if it just got lost amidst this rather busy list:
>
> https://lore.kernel.org/platform-driver-x86/adg6GzkykThAB_4u@djouze-zen/
>
> Thank you for your time, and sorry for any inconvenience.
Okay. The patch seems to be sitting in the queue like it should be.
Pending patches can always be viewed from there (MAINTAINERS file also
has this link):
https://patchwork.kernel.org/project/platform-driver-x86/list/
I (as the maintainer) won't forget any patch that appears on that list.
I admit though catching myself a few times accidently closing a patch as
"accepted" when I did not do the last apply step of my workflow. If a
patch ever happens to suffer from such an unfortunate fate, it does
not appear in either review-ilpo-* branch nor in the patchwork anymore,
pinging is definitely useful (after a few days, there may be small
delays in pushing review-ilpo-* branches out).
--
i.
prev parent reply other threads:[~2026-04-23 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 23:01 José Guilherme de Castro Rodrigues
2026-04-02 18:12 ` José Guilherme de Castro Rodrigues
2026-04-09 12:45 ` Ilpo Järvinen
2026-04-22 23:12 ` José Guilherme de Castro Rodrigues
2026-04-23 11:29 ` Ilpo Järvinen [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=88b55672-8cdb-7aa9-634b-da8d59d03bf7@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=benato.denis96@gmail.com \
--cc=corentin.chary@gmail.com \
--cc=hansg@kernel.org \
--cc=jose.guilherme.cr.bh@gmail.com \
--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
Powered by JetHome