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
| ||
|
Date: Tue, 23 Oct 2012 21:52:35 -0700 From: Joe Perches <joe@...ches.com> To: jeffrey.t.kirsher@...el.com Cc: Tushar Dave <tushar.n.dave@...el.com>, davem@...emloft.net, Jesse Brandeburg <jesse.brandeburg@...el.com>, netdev@...r.kernel.org, gospo@...hat.com, sassmann@...hat.com Subject: Re: [net-next 2/8] maintainers: update with official intel support link, new maintainer On Tue, 2012-10-23 at 21:32 -0700, Jeff Kirsher wrote: > On Tue, 2012-10-23 at 06:25 -0700, Joe Perches wrote: > > On Tue, 2012-10-23 at 03:24 -0700, Jeff Kirsher wrote: > > > Add the current e1000 maintainer to the list of Intel maintainers. > > Maybe add an internal exploder to get all the various > > maintainers on a list if everyone really looks at all > > patches to intel drivers. > > INTEL ETHERNET DRIVERS > > M: Jeff Kirsher <jeffrey.t.kirsher@...el.com> > > M: Intel Linux Support <linux.drivers@...el.com> > > T: git git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/net.git > > T: git git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/net-next.git > > S: Supported > > F: drivers/net/ethernet/intel/ > I understand where your coming from and this has been been something > that I have been trying to find a "reasonable" solution, which is harder > to do than one would expect. [] > So how do we go about giving this spider web of complex coverage to some > clear concise coverage in the MAINTAINERS? [] > If you have some ideas which may help resolve the issues, I am open to > suggestions. It's great that they all work on all intel drivers, but it seems that you are the nominal maintainer and they are all developers that might work on anything but nothing in particular. I think an internal exploder email address would work well. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists