From: Nick Winlund <nwinlu@comcast.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Adrian Bunk <bunk@stusta.de>, Benjamin LaHaise <bcrl@kvack.org>,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] kill include/linux/eeprom.h
Date: Thu, 17 Feb 2005 10:53:29 -0800 [thread overview]
Message-ID: <4214E829.8040202@comcast.net> (raw)
In-Reply-To: <4214E419.5060807@pobox.com>
I agree eeprom is memory technology at the least there should be
secondary links for a static or symlinked file that leaves PCI/AT boot
devices, future PLOS open to development.
Nick
> I would rather update other drivers to use it :)
>
> Jeff
>
>
>
> -
> 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-02-17 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 14:48 [2.6 patch] kill include/linux/eeprom.h Adrian Bunk
2005-02-17 18:36 ` Jeff Garzik
2005-02-17 18:53 ` Nick Winlund [this message]
2005-02-17 19:10 ` Adrian Bunk
-- 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=4214E829.8040202@comcast.net \
--to=nwinlu@comcast.net \
--cc=bcrl@kvack.org \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
/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