From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Erim, Salih" <Salih.Erim@amd.com>,
"O'Griofa, Conall" <conall.ogriofa@amd.com>,
"jic23@kernel.org" <jic23@kernel.org>
Cc: "dlechner@baylibre.com" <dlechner@baylibre.com>,
"nuno.sa@analog.com" <nuno.sa@analog.com>,
"andy@kernel.org" <andy@kernel.org>,
"Simek, Michal" <michal.simek@amd.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Update xilinx-ams driver maintainers
Date: Wed, 20 Aug 2025 11:45:16 +0200 [thread overview]
Message-ID: <44c20b00-a71e-4d1f-8d73-d4255025d9ab@kernel.org> (raw)
In-Reply-To: <IA1PR12MB7736460C9ACC449D58F992559F33A@IA1PR12MB7736.namprd12.prod.outlook.com>
On 20/08/2025 11:10, Erim, Salih wrote:
>> We see that from the diff. Don't write what is obvious. Explain what is not obvious:
>> why you are doing this.
>
> As Michal explained, Anand left AMD while ago. Me and Conall continue to maintain the driver.
>
> Thanks for warning, I will be careful about future comments and communications.
>
No, your commit msg should explain that. Do not say what you do.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-08-20 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 15:04 [PATCH] MAINTAINERS: Update xilinx-ams driver maintainers Salih Erim
2025-08-19 15:10 ` O'Griofa, Conall
2025-08-19 17:45 ` Jonathan Cameron
2025-08-19 18:28 ` Andy Shevchenko
2025-08-19 15:16 ` Michal Simek
2025-08-20 6:11 ` Krzysztof Kozlowski
2025-08-20 9:10 ` Erim, Salih
2025-08-20 9:45 ` 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=44c20b00-a71e-4d1f-8d73-d4255025d9ab@kernel.org \
--to=krzk@kernel.org \
--cc=Salih.Erim@amd.com \
--cc=andy@kernel.org \
--cc=conall.ogriofa@amd.com \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=nuno.sa@analog.com \
/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).