From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Daniel Peng(彭博煜_Pegatron)" <Daniel_Peng@pegatroncorp.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"daniel_peng@pegatron.corp-partner.google.com"
<daniel_peng@pegatron.corp-partner.google.com>
Subject: Re: [PATCH 1/2] dt-bindings: HID: i2c-hid: elan: Introduce FocalTech FT8112
Date: Tue, 11 Nov 2025 10:10:50 +0100 [thread overview]
Message-ID: <f0636e96-7c27-47bf-97e0-0497eb268d8d@kernel.org> (raw)
In-Reply-To: <SEZPR06MB67428F386E3E56D0710AC7EBE7CFA@SEZPR06MB6742.apcprd06.prod.outlook.com>
On 11/11/2025 09:35, Daniel Peng(彭博煜_Pegatron) wrote:
> Remove added members.
>
> Sorry to send duplicated them. This is my first time to process the upstream.
> Could you help to confirm how to version my patches correctly?
And kernel docs don't explain that? There are multiple guidelines in
internet, multiple talks describing it, so I don't think that me
repeating the same again is needed.
Please version your patches correctly, e.g. use b4 or git format-patch
-vX, and add changelog in cover letter or under '---' of individual
patches describing changes from previous version.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-11-11 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 1:34 [PATCH 1/2] dt-bindings: HID: i2c-hid: elan: Introduce FocalTech FT8112 daniel_peng
2025-11-11 2:31 ` Rob Herring (Arm)
2025-11-11 7:23 ` Krzysztof Kozlowski
2025-11-11 7:18 ` Pin-yen Lin
2025-11-11 7:50 ` Daniel Peng(彭博煜_Pegatron)
2025-11-11 8:21 ` Krzysztof Kozlowski
2025-11-11 8:35 ` Daniel Peng(彭博煜_Pegatron)
2025-11-11 9:10 ` Krzysztof Kozlowski [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=f0636e96-7c27-47bf-97e0-0497eb268d8d@kernel.org \
--to=krzk@kernel.org \
--cc=Daniel_Peng@pegatroncorp.com \
--cc=conor+dt@kernel.org \
--cc=daniel_peng@pegatron.corp-partner.google.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).