netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Kumar Gala <kumar.gala@freescale.com>,
	Netdev <netdev@oss.sgi.com>,
	David Woodhouse <dwmw2@infradead.org>, jamal <hadi@cyberus.ca>
Subject: Re: [RFR] gianfar ethernet driver
Date: Fri, 9 Jul 2004 00:35:37 +0100	[thread overview]
Message-ID: <20040708233537.GA20763@infradead.org> (raw)
In-Reply-To: <40EDD7F1.6090309@pobox.com>

On Thu, Jul 08, 2004 at 07:25:37PM -0400, Jeff Garzik wrote:
> Christoph Hellwig wrote:
> >Are you sure someone ever tried building this driver modular?  The 
> >makefile
> >would try to build it into three separate modules, and they'd fail to load
> >due to unresolved cross-depencies..
> 
> 
> For embedded drivers isn't not uncommon that it's never used as a 
> module, so it wouldn't surprise me.

then it shouldn't be declare tristate at least.  But given that modularizig
a netdriver is trivial not doing so counts as a bug to me.

  reply	other threads:[~2004-07-08 23:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8F52CF1D-C916-11D8-BB6A-000393DBC2E8@freescale.com>
2004-07-05 17:28 ` [RFR] gianfar ethernet driver Jeff Garzik
2004-07-06  2:38   ` jamal
     [not found]   ` <20040708231131.GA20305@infradead.org>
2004-07-08 23:25     ` Jeff Garzik
2004-07-08 23:35       ` Christoph Hellwig [this message]
     [not found]   ` <1089375760.28614.1365.camel@hades.cambridge.redhat.com>
2004-07-09 16:47     ` Phy layer notes (was Re: [RFR] gianfar ethernet driver) Jeff Garzik
     [not found] <C681B01E-CEA9-11D8-931F-000393DBC2E8@freescale.com>
     [not found] ` <89563A5C-CFAE-11D8-BA44-000393C30512@freescale.com>
2004-07-07  3:18   ` [RFR] gianfar ethernet driver jamal
2004-07-07  3:29     ` Jeff Garzik
2004-07-07  3:41       ` jamal
2004-07-07  5:35         ` Jeff Garzik
2004-07-07 18:29           ` jamal
     [not found]             ` <40EDC7A7.8060906@pobox.com>
2004-07-08 23:08               ` jamal
2004-07-21 19:51       ` Andy Fleming
2004-07-21 20:14         ` David Woodhouse
2004-08-02 22:19       ` Andy Fleming
2004-08-02 23:11         ` Jeff Garzik
2004-08-02 23:25           ` Andy Fleming
2004-08-04 23:02             ` Andy Fleming
2004-08-16 16:31               ` Kumar Gala
2004-08-22 21:03               ` Jeff Garzik
2004-07-07  5:27   ` Jeff Garzik
     [not found]     ` <D3458628-D05D-11D8-BA44-000393C30512@freescale.com>
2004-07-08 22:29       ` Jeff Garzik
     [not found]         ` <944A2374-D137-11D8-8835-000393C30512@freescale.com>
2004-07-09  1:32           ` jamal
2004-07-09  1:42             ` jamal
2004-07-26 22:06     ` Andy Fleming
2004-07-26 22:10       ` Jeff Garzik
2004-08-02 13:59         ` Kumar Gala
2004-08-02 14:09           ` Christoph Hellwig
2004-08-02 14:11             ` Kumar Gala
     [not found] ` <2A724364-D53A-11D8-8835-000393C30512@freescale.com>
     [not found]   ` <40F4A6E5.4060000@pobox.com>
2004-07-19 23:29     ` Andy Fleming
2004-07-20  1:13       ` David Woodhouse

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=20040708233537.GA20763@infradead.org \
    --to=hch@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=hadi@cyberus.ca \
    --cc=jgarzik@pobox.com \
    --cc=kumar.gala@freescale.com \
    --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).