From: Jiri Slaby <jirislaby@kernel.org>
To: "Gupta, Nipun" <nipun.gupta@amd.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: tglx@linutronix.de, maz@kernel.org, linux-kernel@vger.kernel.org,
Nikhil Agarwal <nikhil.agarwal@amd.com>
Subject: Re: [PATCH] irqdomain: cdx: Switch to of_fwnode_handle()
Date: Wed, 16 Apr 2025 07:14:59 +0200 [thread overview]
Message-ID: <3bd616cf-1655-4700-8c84-e26e71c43edf@kernel.org> (raw)
In-Reply-To: <929198a2-6b3b-0f1b-3f36-cd8955ca6f19@amd.com>
On 16. 04. 25, 7:06, Gupta, Nipun wrote:
>
>
> On 16-04-2025 10:28, Jiri Slaby wrote:
>> On 16. 04. 25, 6:30, Gupta, Nipun wrote:
>>> This will go via Greg's char-misc tree.
>>
>> Ah, then I should've sent this to him in the first place :). Uhm, but
>> MAINTAINERS says:
>> AMD CDX BUS DRIVER
>> M: Nipun Gupta <nipun.gupta@amd.com>
>> M: Nikhil Agarwal <nikhil.agarwal@amd.com>
>> S: Maintained
>> F: Documentation/devicetree/bindings/bus/xlnx,versal-net-cdx.yaml
>> F: drivers/cdx/*
>> F: include/linux/cdx/*
>
> As a MAINTAINER, I/Nikhil need to review. We do not maintain a tree and
> patches go via Greg's tree.
Yes, I understand, but how are patches supposed to reach him? If he
maintains this in his tree, perhaps drivers/cdx/* deserves an entry in
the MISC entry too?
--
js
suse labs
prev parent reply other threads:[~2025-04-16 5:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 10:47 [PATCH] irqdomain: cdx: Switch to of_fwnode_handle() Jiri Slaby (SUSE)
2025-04-16 4:30 ` Gupta, Nipun
2025-04-16 4:58 ` Jiri Slaby
2025-04-16 5:05 ` Greg KH
2025-04-16 5:06 ` Gupta, Nipun
2025-04-16 5:14 ` Jiri Slaby [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=3bd616cf-1655-4700-8c84-e26e71c43edf@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.com \
--cc=tglx@linutronix.de \
/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