lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3bd616cf-1655-4700-8c84-e26e71c43edf@kernel.org>
Date: Wed, 16 Apr 2025 07:14:59 +0200
From: Jiri Slaby <jirislaby@...nel.org>
To: "Gupta, Nipun" <nipun.gupta@....com>, Greg KH <gregkh@...uxfoundation.org>
Cc: tglx@...utronix.de, maz@...nel.org, linux-kernel@...r.kernel.org,
 Nikhil Agarwal <nikhil.agarwal@....com>
Subject: Re: [PATCH] irqdomain: cdx: Switch to of_fwnode_handle()

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@....com>
>> M:      Nikhil Agarwal <nikhil.agarwal@....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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ