From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arnav Kapoor <kapoorarnav43@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Gwendal Grignou" <gwendal@chromium.org>,
"Daniel Campello" <campello@chromium.org>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Semtech SX9xxx: add a reviewer entry and binding maintainer
Date: Wed, 18 Nov 2026 14:14:30 +0100 [thread overview]
Message-ID: <b6b12988-7d36-4cbb-bdaf-1deb7203b9ac@kernel.org> (raw)
In-Reply-To: <20261118125450.12512-1-kapoorarnav43@gmail.com>
On 18/11/2026 13:54, Arnav Kapoor wrote:
> On Wed, Nov 18, 2026 at 01:34:31PM +0100, Krzysztof Kozlowski wrote:
>> I think it is premature. You just started contributing and your early
>> submissions were clearly showing that you did not read kernel docs
>> before posting.
>
> Hi Krzysztof,
>
> In June I was still figuring out git send-email, and a problem with my
> setup caused those repeated postings. It is also why I was not able to
> reply to you at the time. I have since worked through the process
> documentation and my setup.
>
> Since then I have been working steadily on this subsystem, and 23 of
> my commits are now in maintainer trees. I still make mistakes as I
> learn: not grouping patches into a series, writing commit messages that
> are too long, and sending new versions too early, as Andy pointed out
> here. Changing MAINTAINERS is new to me as well, so there are mistakes
> in this series too. I take those as part of the learning process.
>
> I asked for this entry because I have become interested in these
> drivers and want to keep working on them, and Jonathan agreed to an R:
> entry. I understand your concern. If there is something specific you
> would like to see before this entry is acceptable, please tell me and
> I will work on it.
You can review patches and follow them easily with lei or korgalore. You
do not have to be listed as maintainer to do that.
I am sorry, but sending us LLM slop (so code which was never built) is
very opposite to being a maintainer.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-11-18 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 17:26 [PATCH v3 0/2] Semtech SX9xxx: add a reviewer entry and binding maintainer Arnav Kapoor
2026-11-17 17:26 ` [PATCH v3 1/2] dt-bindings: iio: proximity: semtech: add myself as maintainer Arnav Kapoor
2026-11-18 12:37 ` Krzysztof Kozlowski
2026-11-17 17:26 ` [PATCH v3 2/2] MAINTAINERS: add a reviewer entry for the Semtech SX9xxx proximity drivers Arnav Kapoor
2026-11-17 19:17 ` [PATCH v3 0/2] Semtech SX9xxx: add a reviewer entry and binding maintainer Andy Shevchenko
2026-11-18 7:36 ` Joshua Crofts
2026-11-18 11:31 ` Andy Shevchenko
2026-11-18 12:34 ` Krzysztof Kozlowski
2026-11-18 12:54 ` Arnav Kapoor
2026-11-18 13:14 ` 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=b6b12988-7d36-4cbb-bdaf-1deb7203b9ac@kernel.org \
--to=krzk@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=campello@chromium.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=gwendal@chromium.org \
--cc=jic23@kernel.org \
--cc=kapoorarnav43@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.