From: Ben Dooks <ben-linux@fluff.org>
To: David Miller <davem@davemloft.net>
Cc: s-jan@ti.com, netdev@vger.kernel.org, linux-omap@vger.kernel.org,
x0066660@ti.com, ben-linux@fluff.org, Tristram.Ha@micrel.com
Subject: Re: [PATCH 2/4 v2] ks8851: Low level functions for read/write to companion eeprom
Date: Tue, 11 May 2010 02:23:54 +0100 [thread overview]
Message-ID: <20100511012353.GJ2589@trinity.fluff.org> (raw)
In-Reply-To: <20100506.002012.27799102.davem@davemloft.net>
On Thu, May 06, 2010 at 12:20:12AM -0700, David Miller wrote:
> From: Sebastien Jan <s-jan@ti.com>
> Date: Wed, 5 May 2010 20:45:53 +0200
>
> > Low-level functions provide 16bits words read and write capability
> > to ks8851 companion eeprom.
> >
> > Signed-off-by: Sebastien Jan <s-jan@ti.com>
>
> Applied.
So I take it the patches that used the drivers/misc/eeprom/eeprom_93cx6.c
are not going to be merged?
--
Ben
Q: What's a light-year?
A: One-third less calories than a regular year.
next prev parent reply other threads:[~2010-05-11 1:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 18:45 [PATCH 0/4 v2] ks8851: support for read/write MAC address from eeprom Sebastien Jan
2010-05-05 18:45 ` [PATCH 1/4 v2] ks8851: Add caching of CCR register Sebastien Jan
2010-05-06 7:20 ` David Miller
2010-05-05 18:45 ` [PATCH 2/4 v2] ks8851: Low level functions for read/write to companion eeprom Sebastien Jan
2010-05-06 7:20 ` David Miller
2010-05-11 1:23 ` Ben Dooks [this message]
2010-05-11 5:59 ` David Miller
2010-05-11 1:16 ` Ben Dooks
2010-05-05 18:45 ` [PATCH 3/4 v2] ks8851: companion eeprom access through ethtool Sebastien Jan
2010-05-06 7:20 ` David Miller
2010-05-05 18:45 ` [PATCH 4/4 v2] ks8851: read/write MAC address on companion eeprom through debugfs Sebastien Jan
2010-05-06 7:25 ` David Miller
2010-05-06 8:01 ` Sebastien Jan
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=20100511012353.GJ2589@trinity.fluff.org \
--to=ben-linux@fluff.org \
--cc=Tristram.Ha@micrel.com \
--cc=davem@davemloft.net \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s-jan@ti.com \
--cc=x0066660@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.