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
| ||
|
Message-ID: <dc252e61-3179-4f51-90e6-f92929e93d40@BN1AFFO11FD030.protection.gbl> Date: Tue, 22 Jul 2014 19:02:08 +0200 From: Michal Simek <michal.simek@...inx.com> To: Bjorn Helgaas <bhelgaas@...gle.com>, Srikanth Thokala <sthokal@...inx.com> CC: Michal Simek <michal.simek@...inx.com>, Grant Likely <grant.likely@...aro.org>, Rob Herring <robh+dt@...nel.org>, Arnd Bergmann <arnd@...db.de>, "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org> Subject: Re: [PATCH v4] pcie: Add Xilinx PCIe Host Bridge IP driver On 07/22/2014 06:08 PM, Bjorn Helgaas wrote: > On Mon, Jul 21, 2014 at 11:10 PM, Srikanth Thokala <sthokal@...inx.com> wrote: >> On Wed, Jul 16, 2014 at 11:08 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote: >>> ... >>> I see I forgot to ask for a MAINTAINERS entry for this driver. Can >>> you add one? >> >> There was a discussion on this earlier and Michal mentioned it is not >> required as it is >> handled by our Xilinx record. >> >> Here is the reply from Michal to the MAINTAINERS update comment, >> >> < Reply from Michal > >> >>> Please also include a MAINTAINERS update for drivers/pci/host/pci-xilinx.c. >> >> This should be handle by our record that's why MAINTAINERS update is >> not necessary. >> (N: xilinx below) > > That's technically true in the sense that get_maintainer.pl will do > the right thing, but I often review patches in email (without > extracting them), so it's more convenient to just look in MAINTAINERS > to see if they have the right acks. But I guess I can deal with it > either way. There is also another reason for using just this fragment. Because developers and their responsibilities are changing so often and I just know who is responsible for it at that time. Thanks, Michal -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists