On Tue, 2012-10-23 at 21:52 -0700, Joe Perches wrote:
On Tue, 2012-10-23 at 21:32 -0700, Jeff Kirsher wrote:
quoted
On Tue, 2012-10-23 at 06:25 -0700, Joe Perches wrote:
quoted
On Tue, 2012-10-23 at 03:24 -0700, Jeff Kirsher wrote:
quoted
quoted
quoted
Add the current e1000 maintainer to the list of Intel maintainers.
quoted
quoted
Maybe add an internal exploder to get all the various
maintainers on a list if everyone really looks at all
patches to intel drivers.
quoted
quoted
INTEL ETHERNET DRIVERS
M: Jeff Kirsher [off-list ref]
M: Intel Linux Support [off-list ref]
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/
quoted
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.
[]
quoted
So how do we go about giving this spider web of complex coverage to some
clear concise coverage in the MAINTAINERS?
[]
quoted
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.
That sounds good, I will discuss it with guys and figure it out.
Thanks!