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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 16 Sep 2021 14:49:37 +0000 From: Min Li <min.li.xe@...esas.com> To: Greg KH <gregkh@...uxfoundation.org> CC: "arnd@...db.de" <arnd@...db.de>, "derek.kiernan@...inx.com" <derek.kiernan@...inx.com>, "dragan.cvetic@...inx.com" <dragan.cvetic@...inx.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "lee.jones@...aro.or" <lee.jones@...aro.or> Subject: RE: [PATCH misc v2 1/2] mfd: rsmu: Resolve naming conflict between idt8a340_reg.h and idt82p33_reg.h > > > > Wait, how can this patch on its own not break things? Are there no > in-kernel users of these symbols today? If not, why is this file in > here? > > confused, > > greg k-h Yes, it is standalone now but it would be used by this driver and another PHC driver that I will submit later. This file provides register definitions and belongs to the MFD change I submitted before. The MFD driver will spawn 2 devices 1) ptp hardware clock device 2) This RSMU misc device The plan is 1) submit mfd change 2) submit misc change 3) submit phc change Min
Powered by blists - more mailing lists