From: Nathan Chancellor <nathan@kernel.org>
To: Denis Benato <denis.benato@linux.dev>
Cc: "Paolo Pisati" <p.pisati@gmail.com>,
"Jiri Kosina" <jikos@kernel.org>,
"Benjamin Tissoires" <bentiss@kernel.org>,
"Luke Jones" <luke@ljones.dev>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Joshua Leivenzon" <hacker1024@users.sourceforge.net>,
"Ivan Levchenko" <me@livan.pro>,
"Rebecca Mara Müller" <rebecca.mara@posteo.de>
Subject: Re: [PATCH v3 6/7] HID: asus: add prod-id, quirk for Zenbook Duo keyboard
Date: Sun, 18 Oct 2026 14:43:26 -0700 [thread overview]
Message-ID: <20261018214326.GC4068315@ax162> (raw)
In-Reply-To: <42cfc8c8-869f-41e2-a58c-0d6c5ce4a6ba@linux.dev>
On Sun, Oct 18, 2026 at 06:57:16PM +0200, Denis Benato wrote:
>
> On 10/13/26 12:40, Paolo Pisati wrote:
> > From: Luke Jones <luke@ljones.dev>
>
> A piece of mail header opening a commit? Never seen this.
>
> I'd say remove this: that this comes from Luke can be deducted
> in the Signed-off-by.
>
> My question is why has this not been accepted before? Did I miss
> this while we transitioned maintainer? If so apologies.
This is standard git send-email behavior to signify that Luke should be
the author in git when this patch is applied via 'git am' but Paolo is
the one sending it. If Luke originally authored this patch, then he
should proabably be the author in git history, especially since the
signoff chain would make no sense otherwise.
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-10-18 21:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 10:39 [PATCH v3 0/7] HID: asus: ASUS Zenbook Duo keyboard support Paolo Pisati
2026-10-13 10:39 ` [PATCH v3 1/7] HID: asus: Fix up Zenbook Duo report descriptors Paolo Pisati
2026-10-18 15:50 ` Denis Benato
2026-10-18 16:18 ` Rebecca Mara Müller
2026-10-18 17:52 ` Denis Benato
2026-10-13 10:39 ` [PATCH v3 2/7] HID: asus: Add missing Zenbook Duo hotkeys Paolo Pisati
2026-10-18 15:55 ` Denis Benato
2026-10-18 21:38 ` Nathan Chancellor
2026-10-18 21:39 ` Denis Benato
2026-10-13 10:40 ` [PATCH v3 3/7] HID: asus: Force hid-input to bind to the Zenbook Duo hotkey interface Paolo Pisati
2026-10-18 16:06 ` Denis Benato
2026-10-13 10:40 ` [PATCH v3 4/7] HID: asus: Cycle the platform profile from the Zenbook Duo profile key Paolo Pisati
2026-10-18 16:27 ` Denis Benato
2026-10-13 10:40 ` [PATCH v3 5/7] HID: asus: Do not send feature reports larger than declared Paolo Pisati
2026-10-18 16:52 ` Denis Benato
2026-10-13 10:40 ` [PATCH v3 6/7] HID: asus: add prod-id, quirk for Zenbook Duo keyboard Paolo Pisati
2026-10-18 16:57 ` Denis Benato
2026-10-18 21:43 ` Nathan Chancellor [this message]
2026-10-18 21:46 ` Denis Benato
2026-10-13 10:40 ` [PATCH v3 7/7] HID: asus: Re-send the Zenbook Duo keyboard handshake after probe Paolo Pisati
2026-10-18 17:10 ` Denis Benato
2026-10-18 19:18 ` Rebecca Mara Müller
2026-10-18 19:48 ` Denis Benato
2026-10-19 6:12 ` Rebecca Mara Müller
2026-10-19 11:03 ` Denis Benato
2026-10-13 11:45 ` [PATCH v3 0/7] HID: asus: ASUS Zenbook Duo keyboard support Rebecca Mara Müller
2026-10-13 13:56 ` Denis Benato
2026-10-14 13:21 ` Paolo Pisati
2026-10-18 17:21 ` Denis Benato
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=20261018214326.GC4068315@ax162 \
--to=nathan@kernel.org \
--cc=bentiss@kernel.org \
--cc=denis.benato@linux.dev \
--cc=hacker1024@users.sourceforge.net \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=me@livan.pro \
--cc=p.pisati@gmail.com \
--cc=rebecca.mara@posteo.de \
/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®