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: Tue, 10 Aug 2021 03:07:13 -0700 From: Florian Fainelli <f.fainelli@...il.com> To: Jeremy Linton <jeremy.linton@....com>, linux-pci@...r.kernel.org Cc: lorenzo.pieralisi@....com, nsaenz@...nel.org, bhelgaas@...gle.com, rjw@...ysocki.net, lenb@...nel.org, robh@...nel.org, kw@...ux.com, f.fainelli@...il.com, bcm-kernel-feedback-list@...adcom.com, linux-acpi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-rpi-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/3] PCI: brcmstb: Break register definitions into separate header On 8/5/2021 2:11 PM, Jeremy Linton wrote: > We are about to create a standalone ACPI quirk module for the > bcmstb controller. Lets move the register definitions into a separate > file so they can be shared between the APCI quirk and the normal > host bridge driver. > > Signed-off-by: Jeremy Linton <jeremy.linton@....com> > --- > drivers/pci/controller/pcie-brcmstb.c | 179 +------------------------ > drivers/pci/controller/pcie-brcmstb.h | 182 ++++++++++++++++++++++++++ > 2 files changed, 183 insertions(+), 178 deletions(-) > create mode 100644 drivers/pci/controller/pcie-brcmstb.h You moved more than just register definitions into pcie-brcmstb.h you also moved internal structure definitions, enumerations, etc. which are not required since pcie-brcmstb-acpi.c does not access the brcm_pcie structure but open codes accesses to the MISC_STATUS register instead. There are no include guards added to this file (it is debatable whether we should add them), and it is also not covered by the existing BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE MAINTAINERS file entry. Given that there can be new platforms supported by this PCIe controller in the future possibly with the same limitations as the 2711, but with a seemingly different MISC_STATUS layout, you will have to think about a solution that scales, maybe we cross that bridge when we get there. -- Florian
Powered by blists - more mailing lists