From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nina_Kuo@novatek.com.tw
Cc: andi.shyti@kernel.org, ben_huang@novatek.com.tw,
conor+dt@kernel.org, devicetree@vger.kernel.org,
krzk+dt@kernel.org, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
shihpei_hsu@novatek.com.tw, toby_chui@novatek.com.tw
Subject: Re: [PATCH v3 1/3] MAINTAINERS: Add entry for Novatek NT726xx SoC I2C controller driver
Date: Tue, 21 Jul 2026 10:08:32 +0200 [thread overview]
Message-ID: <25ae1ecc-b7f1-4132-81f9-7bb91f1a5d3d@kernel.org> (raw)
In-Reply-To: <20260721080042.472564-1-Nina_Kuo@novatek.com.tw>
On 21/07/2026 10:00, Nina_Kuo@novatek.com.tw wrote:
> From: Ben Huang <Ben_Huang@novatek.com.tw>
>
> Hi,
>
> Thanks for your reviewing.
>
> Sorry about the same mistake. This is the first time for
> submitting kernel patches.
> To fix this problem, shall I put all modifications into 1 patch
> file? Please correct me if I'm wrong.
>
> In the patch series, MAINTAINERS is in the first patch (1/3),
> related .yaml (2/3) and .c (3/3) files are in the subsequent
> patches.
> If only MAINTAINTERS patch is applied, neither .yaml nor .c can
> be found under kernel source codes. I think this is the question
> you mentioned. Please correct me if I'm wrong.
Please do not top post or remove context you are replying to. I have
like 200+ emails per day, so what is this about?
Please learn how Git works, how its history is organized, how commits
link to each other. This is nothing specific to submitting patches or
kernel development - this is basics of Git with combination of
bisectability of software development cycles.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-07-21 8:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 7:34 [PATCH v3 0/3] i2c: Add Novatek NT726xx SoC I2C controller Nina_Kuo
2026-07-15 7:35 ` [PATCH v3 1/3] MAINTAINERS: Add entry for Novatek NT726xx SoC I2C controller driver Nina_Kuo
2026-07-15 7:35 ` [PATCH v3 2/3] dt-bindings: i2c: Add Novatek NT726xx SoC I2C controller Nina_Kuo
2026-07-15 7:35 ` [PATCH v3 3/3] i2c: Add i2c-nt726xx.c I2C driver for Novatek NT726xx SoCs Nina_Kuo
2026-07-21 7:14 ` Krzysztof Kozlowski
2026-07-22 2:41 ` nina_kuo
2026-07-21 7:10 ` [PATCH v3 2/3] dt-bindings: i2c: Add Novatek NT726xx SoC I2C controller Krzysztof Kozlowski
2026-07-22 2:22 ` nina_kuo
2026-07-22 6:12 ` Krzysztof Kozlowski
2026-07-22 6:29 ` nina_kuo
2026-07-21 7:11 ` [PATCH v3 1/3] MAINTAINERS: Add entry for Novatek NT726xx SoC I2C controller driver Krzysztof Kozlowski
2026-07-21 7:16 ` Krzysztof Kozlowski
2026-07-21 8:00 ` Nina_Kuo
2026-07-21 8:08 ` Krzysztof Kozlowski [this message]
2026-07-22 1:40 ` SP_ISW1_AT
2026-07-22 1:42 ` nina_kuo
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=25ae1ecc-b7f1-4132-81f9-7bb91f1a5d3d@kernel.org \
--to=krzk@kernel.org \
--cc=Nina_Kuo@novatek.com.tw \
--cc=andi.shyti@kernel.org \
--cc=ben_huang@novatek.com.tw \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shihpei_hsu@novatek.com.tw \
--cc=toby_chui@novatek.com.tw \
/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®