mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Niravkumar L Rabara <niravkumarlaxmidas.rabara@altera.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	matthew.gerlach@altera.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Change Altera socfpga-ecc-manager.yaml maintainer
Date: Fri, 17 Oct 2025 14:14:22 +0800	[thread overview]
Message-ID: <9281bade-0d14-4fbc-870a-120101dc3a67@altera.com> (raw)
In-Reply-To: <b331600f-af5f-40b1-8acf-007044fd34f3@kernel.org>



On 17/10/2025 12:36 pm, Krzysztof Kozlowski wrote:
> On 17/10/2025 05:27, niravkumarlaxmidas.rabara@altera.com wrote:
>> From: Niravkumar L Rabara <niravkumarlaxmidas.rabara@altera.com>
>>
>> Update Altera socfpga-ecc-manager dt bindings maintainer from
>> <matthew.gerlach@altera.com> to <niravkumarlaxmidas.rabara@altera.com>
>> as Matthew Gerlack is moving out of Altera.
>>
>> Signed-off-by: Niravkumar L Rabara <niravkumarlaxmidas.rabara@altera.com>
>> Acked-by: Matthew Gerlach <matthew.gerlach@altera.com>
>> ---
>>
>> Resending the patch with complete maintainer list.
>> Link to previous patch Acked-by Matthew Gerlach
>> https://lore.kernel.org/lkml/91cd7ccb-e821-48de-8d52-f8889af80a08@altera.com/
> 
> 
> So that's a RESEND, mark your patches correctly.
> 
> It is great you stepped in to take care about this driver. This also
> means you have new responsibilities, like learning how kernel
> development process works, including how and who takes patches. Please
> learn that so you can send the patch to appropriate people, otherwise it
> probably won't be applied. For example I do not apply patches of which I
> am not aware of. I know that many maintainers follow similar rule.
> 
> 
> Best regards,
> Krzysztof

Noted Krzysztof. I will take care next time.

I just realized that I have made another mistake, I supposed to update 
the maintainer name in yaml bindings as well, which I missed.

I will send v2 patch with this change.

Thanks,
Nirav

  reply	other threads:[~2025-10-17  6:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  3:27 niravkumarlaxmidas.rabara
2025-10-17  4:36 ` Krzysztof Kozlowski
2025-10-17  6:14   ` Niravkumar L Rabara [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-09 14:46 niravkumarlaxmidas.rabara
2025-09-09 15:30 ` Matthew Gerlach

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=9281bade-0d14-4fbc-870a-120101dc3a67@altera.com \
    --to=niravkumarlaxmidas.rabara@altera.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.gerlach@altera.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 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®