From: Michael Wu <flamingice-R9e9/4HEdknk1uMJSBkQmQ@public.gmane.org>
To: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
John Linville <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
Ivo van Doorn <ivdoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 1/2] Add 93cx6 eeprom library
Date: Mon, 7 May 2007 11:40:25 -0400 [thread overview]
Message-ID: <200705071140.29435.flamingice@sourmilk.net> (raw)
In-Reply-To: <20070507142715.GB32546-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
On Monday 07 May 2007 10:27, Ben Dooks wrote:
> On Mon, May 07, 2007 at 03:46:04AM -0400, Michael Wu wrote:
> > From: Ivo van Doorn <ivdoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >
> > This patch adds a library for reading from and writing to 93cx6 eeproms.
>
> This looks remarkably like an SPI device, why not use the
> spi framework to drive this?
>
Yeah, it's SPI/microwire. As for using the SPI framework.. I dunno. The rt2x00
drivers depend on this too and I'd rather not change the code at this point
since it's well tested and working. Thanks for the heads up about using SPI,
however. I (or maybe Ivo if he has any time) will check the SPI framework
later and see if that simplifies things.
-Michael Wu
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-05-07 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 7:46 [PATCH 1/2] Add 93cx6 eeprom library Michael Wu
[not found] ` <200705070346.04982.flamingice-R9e9/4HEdknk1uMJSBkQmQ@public.gmane.org>
2007-05-07 7:53 ` Ivo van Doorn
2007-05-07 14:27 ` Ben Dooks
[not found] ` <20070507142715.GB32546-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2007-05-07 15:34 ` John W. Linville
2007-05-07 15:40 ` Michael Wu [this message]
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=200705071140.29435.flamingice@sourmilk.net \
--to=flamingice-r9e9/4hedknk1umjsbkqmq@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=ivdoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).