From: Nick Winlund <nwinlu@comcast.net>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Adrian Bunk <bunk@stusta.de>,
jgarzik@pobox.com, linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [2.6 patch] kill include/linux/eeprom.h
Date: Tue, 19 Apr 2005 07:09:38 -0700 [thread overview]
Message-ID: <42651122.30906@comcast.net> (raw)
In-Reply-To: <20050419135648.GC7315@kvack.org>
No I think the eeprom routine should be saved as it is now for niche
vendors and hobbyists. At the very least an accessible versions
repository or CVS containing all prior versions of eeprom implementation
should be available, a la a new " bitkeeper " or whatever retrieval
interface Linus and collaborators decide on.
One project where linux+eeprom may be used:
http://www.ethernut.de/api/if__var_8h.html
Nut OS API
int NutNetLoadConfig (CONST char *name)
Load network configuration from EEPROM.
int NutNetSaveConfig (void)
Save network configuration in EEPROM.
Nick
Benjamin LaHaise wrote:
> At the very least your patch doesn't do a thorough enough job of
> removing the dead code -- there is no good reason to move the unused
> code into ns83820.c.
>
> Also, someone needs to go around refactoring eeprom code out of the
> network drivers at some point.
>
> -ben
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2005-04-19 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 1:29 [2.6 patch] kill include/linux/eeprom.h Adrian Bunk
2005-04-19 13:56 ` Benjamin LaHaise
2005-04-19 14:09 ` Nick Winlund [this message]
2005-04-19 23:56 ` Adrian Bunk
2005-04-20 14:42 ` Benjamin LaHaise
-- strict thread matches above, loose matches on Subject: below --
2005-11-05 19:01 Adrian Bunk
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=42651122.30906@comcast.net \
--to=nwinlu@comcast.net \
--cc=bcrl@kvack.org \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-net@vger.kernel.org \
--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).