netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Tom Herbert <therbert@google.com>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
	netdev@vger.kernel.org, Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: [PATCH] Reduce locking in TX path of forcedth driver
Date: Sat, 22 Dec 2007 21:13:52 -0500	[thread overview]
Message-ID: <476DC460.6030701@garzik.org> (raw)
In-Reply-To: <65634d660712212149ua4f083dw80c65ea884902771@mail.gmail.com>

Tom Herbert wrote:
> 
>     (Tom, you failed to CC the maintainer at NVIDIA, please fix...)
> 
>  
> Jeff,
>  
> Please pardon my naivety, but how would determine who the maintainer at 
> NVDIA is?  The MAINTAINERS file lists an Nvidia maintainer only for the 
> framebuffer driver, and I don't see this specified in the source file.

In general, you want to check with

	git log drivers/net/forcedeth.c

in addition to MAINTAINERS, to see who is actively working on the driver.

In this case, the original authors are largely idle (though still 
respond to emails), and NVIDIA has been doing most of the maintenance 
for the past year or more.

MAINTAINERS certainly wants fixing though, if it doesn't reflect the 
current situation.

	Jeff




      parent reply	other threads:[~2007-12-23  2:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-22  1:41 [PATCH] Reduce locking in TX path of forcedth driver Tom Herbert
2007-12-22  2:54 ` Stephen Hemminger
2007-12-22  3:51   ` Jeff Garzik
     [not found]     ` <65634d660712212149ua4f083dw80c65ea884902771@mail.gmail.com>
2007-12-23  2:13       ` Jeff Garzik [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=476DC460.6030701@garzik.org \
    --to=jeff@garzik.org \
    --cc=aabdulla@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    --cc=therbert@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).