From: "Gupta, Nipun" <nipun.gupta@amd.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Nikhil Agarwal <nikhil.agarwal@amd.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/6] cdx: MAINTAINERS: Explicitly mention Greg who handles patches
Date: Fri, 2 May 2025 12:22:51 +0530 [thread overview]
Message-ID: <c2644e83-89b5-baad-005a-ed578200d956@amd.com> (raw)
In-Reply-To: <86cd570d-416a-49ab-84e3-6bf54873f8eb@linaro.org>
On 02-05-2025 11:57, Krzysztof Kozlowski wrote:
> On 01/05/2025 18:06, Krzysztof Kozlowski wrote:
>> On 01/05/2025 17:59, Greg Kroah-Hartman wrote:
>>> On Wed, Apr 30, 2025 at 08:41:34PM +0200, Krzysztof Kozlowski wrote:
>>>> Patches for CDX bus drivers are applied by Greg Kroah-Hartman, so list
>>>> him in the maintainers entry because otherwise contributors would be
>>>> surprised their patches got lost.
>>>>
>>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>> ---
>>>> MAINTAINERS | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>> index b2c3be5f6131432647dd01f22bbf4bf1c8bde9e6..505d7d45ad7d1c007e89a555264ff8cbeaf6e1f4 100644
>>>> --- a/MAINTAINERS
>>>> +++ b/MAINTAINERS
>>>> @@ -1008,6 +1008,7 @@ F: Documentation/devicetree/bindings/w1/amd,axi-1wire-host.yaml
>>>> F: drivers/w1/masters/amd_axi_w1.c
>>>>
>>>> AMD CDX BUS DRIVER
>>>> +M: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>>
>>> Sorry, but no, I'm not the maintainer of this driver. It's up to the
>>> maintainer(s) of it to send me the patches on to be merged, it is not up
>>> to me to maintain the code at all.
>>>
>> Sure, I understand. I will send a v3 without maintainers patch and I
>> assume the maintainers will pick them up (unless drivers are orphaned).
>
>
> And now I found this:
> https://lore.kernel.org/lkml/929198a2-6b3b-0f1b-3f36-cd8955ca6f19@amd.com/
>
> "We do not maintain a tree and patches go via Greg's tree."
>
> which means that patches won't be picked up. Your email does not pop up
> on b4/get_maintainers. Overall this means cdx driver might be abandoned,
> from contributors point of view.
We usually copy Greg once the patches are reviewed/acked from our side
if he is not already on the list. Do you suggest any alternate approach
in maintaining the drivers like cdx which do not have their own tree?
>
> If that's the case I will send a patch making this orphaned.
>
> More patches which never received any attention or were not picked up:
>
> https://lore.kernel.org/lkml/20250118070833.27201-1-chenqiuji666@gmail.com/
This is applied on the Linux tree.
> https://lore.kernel.org/lkml/20241203084409.2747897-1-abhijit.gangurde@amd.com/
This is also applied on the Linux tree.
> https://lore.kernel.org/lkml/20250425133929.646493-2-robin.murphy@arm.com/
This was recently sent and we will review in the upcoming week.
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-05-02 6:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 18:41 [PATCH v2 0/6] cdx: Minor cleanups Krzysztof Kozlowski
2025-04-30 18:41 ` [PATCH v2 1/6] cdx: Enable compile testing Krzysztof Kozlowski
2025-04-30 18:41 ` [PATCH v2 2/6] cdx: controller: Simplify with dev_err_probe() Krzysztof Kozlowski
2025-04-30 18:41 ` [PATCH v2 3/6] cdx: controller: Drop useless probe success message Krzysztof Kozlowski
2025-04-30 18:41 ` [PATCH v2 4/6] cdx: controller: Do not open-code module_platform_driver() Krzysztof Kozlowski
2025-04-30 18:41 ` [PATCH v2 5/6] cdx: controller: Drop unneeded driver.pm NULL assignment Krzysztof Kozlowski
2025-04-30 18:41 ` [PATCH v2 6/6] cdx: MAINTAINERS: Explicitly mention Greg who handles patches Krzysztof Kozlowski
2025-05-01 15:59 ` Greg Kroah-Hartman
2025-05-01 16:06 ` Krzysztof Kozlowski
2025-05-02 6:27 ` Krzysztof Kozlowski
2025-05-02 6:52 ` Gupta, Nipun [this message]
2025-05-02 6:57 ` Krzysztof Kozlowski
2025-05-02 7:17 ` Greg Kroah-Hartman
2025-05-02 7:52 ` Krzysztof Kozlowski
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=c2644e83-89b5-baad-005a-ed578200d956@amd.com \
--to=nipun.gupta@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.agarwal@amd.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