linux-kernel - Re: [PATCH net-next v3 1/1] ptp: 82p33: move register definitions out of ptp folder

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Tue, 16 Apr 2024 12:09:01 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Min Li <lnimi@...mail.com>, richardcochran@...il.com, lee@...nel.org
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org, Min Li
	 <min.li.xe@...esas.com>
Subject: Re: [PATCH net-next v3 1/1] ptp: 82p33: move register definitions
 out of ptp folder

On Fri, 2024-04-12 at 12:17 -0400, Min Li wrote:
> From: Min Li <min.li.xe@...esas.com>
> 
> Relocate idt82p33 register definitions so that other multi-functional
> devices (such as the future DPLL subsystem hardware driver that are
> currently being developed for Renesas timing devices) can access them.
> 
> Signed-off-by: Min Li <min.li.xe@...esas.com>
> ---
> -Submit to net-next and add driver name suggested by Jakub
> -Name the driver that can benefit from thie change suggested by Jakub

I think that the main point from Jakub was that this patch should be
included/posted with the series introducing the driver actually using
the register definition.

That will also better justify the 'net-next' target. For this bare
patch such target is bit arbitrary (e.g. it could go via Lee's tree,
possibly causing less conflicts).

Thanks,

Paolo