public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: John Levon <movement@marcelothewonderpenguin.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: network driver informations [general NIC, Wireless and e100]
Date: Thu, 01 Aug 2002 20:26:26 -0400	[thread overview]
Message-ID: <3D49D1B2.2010201@mandrakesoft.com> (raw)
In-Reply-To: 20020801174252.GA58488@compsoc.man.ac.uk

John Levon wrote:
> On Thu, Aug 01, 2002 at 08:10:25AM -0400, Jeff Garzik wrote:
> 
> 
>>Al Viro has talked about, long term, making this information available 
>>through a filesystem.  When that happens, your request will have 
>>basically been implemented.
> 
> 
> It would probably help if some of the basic code needed was wrapped in
> an even more "dumbed-down" API - most of the stuff in say pcihpfs is
> generically useful for this sort of configfs thing.
> 
> As more and more minifs's appear (they are trivially easy to write after
> all) we're likely to see more duplication of this code, and the
> resultant missing bug fix propogation


Doubtful -- Al Viro created libfs.c, and understands the basic concept 
of avoiding code duplication :)



  reply	other threads:[~2002-08-02  0:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-31 21:24 network driver informations [general NIC, Wireless and e100] Nico Schottelius
2002-08-01 12:00 ` Gianni Tedesco
2002-08-01 12:10 ` Jeff Garzik
2002-08-01 17:42   ` John Levon
2002-08-02  0:26     ` Jeff Garzik [this message]
2002-08-02 19:19     ` Greg KH
2002-08-04 20:12   ` Nico Schottelius

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=3D49D1B2.2010201@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=movement@marcelothewonderpenguin.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