netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@oss.sgi.com
Subject: Re: Resend: [NETDRV] Merge register_netdev calls
Date: Mon, 20 Sep 2004 15:03:51 -0400	[thread overview]
Message-ID: <414F2997.9030901@pobox.com> (raw)
In-Reply-To: <20040701111914.GA11120@gondor.apana.org.au>

Herbert Xu wrote:
> On Fri, Jun 11, 2004 at 12:08:55PM +1000, herbert wrote:
> 
>>In fact it's really making these ISA/MCA probe() functions more
>>like the ones we have for PCI.
> 
> 
> To illustrate this, let's take the first driver touched by 4/x.
> In 3c503, the function init_module() essentially does
> 
> for each ioaddr
> 	if (do_el2_probe(ioaddr) == 0)
> 		return 0
> 
> And do_el2_probe() just calls el2_probe1() which is similar
> to your average PCI probe function except that the first thing
> it does is to make sure that the device exists at ioaddr.
> 
> This is not that different from PCI where it would look
> like
> 
> for each PCI device matching the vendor/product numbers
> 	if (do_el2_probe(device) == 0)
> 		return 0
> 
> Now before my patch, register_netdev was being called just
> after do_el2_probe() returns.  My patch simply moves it to
> the end of el2_probe1() which is exactly what would happen
> if this were a PCI driver.
> 
> I've rediffed it against your net-drivers-2.6 tree.

so,

there was a lot of churn and I held off on this patch.

could you be convinced to rediff and resend (again)?

	Jeff

  reply	other threads:[~2004-09-20 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01 11:19 Resend: [NETDRV] Merge register_netdev calls Herbert Xu
2004-09-20 19:03 ` Jeff Garzik [this message]
2004-09-25  8:32   ` Herbert Xu
2005-03-23  3:30     ` Jeff Garzik

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=414F2997.9030901@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@oss.sgi.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).