From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Cc: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Moving at24 out of i2c/chips?
Date: Wed, 14 Jan 2009 21:40:38 +0100 [thread overview]
Message-ID: <20090114214038.3d7fbf57@hyperion.delvare> (raw)
In-Reply-To: <200901141211.20681.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
On Wed, 14 Jan 2009 12:11:20 -0800, David Brownell wrote:
> On Wednesday 14 January 2009, Wolfram Sang wrote:
> > as drivers/i2c/chips/ is going to go away, I wondered if Jean would be
> > interested in a patch moving it to drivers/misc/ (best location I could
> > come up with)? David, are you okay with that?
>
> That seems a reasonable place for it, if that directory is going
> away. Might even be worth moving the at25 (SPI eeprom) driver
> there to keep it company, and adding an EEPROM section to Kconfig
> for that directory. (There's some 93x6 support too. Those are a
> flavor of SPI eeprom, but that driver doesn't use the SPI stack.)
Yes, makes sense to me. The old eeprom driver could go along as well.
Thanks for taking care of this!
--
Jean Delvare
next prev parent reply other threads:[~2009-01-14 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 19:35 Moving at24 out of i2c/chips? Wolfram Sang
[not found] ` <20090114193521.GB15315-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-01-14 20:11 ` David Brownell
[not found] ` <200901141211.20681.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2009-01-14 20:40 ` Jean Delvare [this message]
[not found] ` <20090114214038.3d7fbf57-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-01-15 10:03 ` Wolfram Sang
[not found] ` <20090115100322.GA3148-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-01-19 16:18 ` Jean Delvare
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=20090114214038.3d7fbf57@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@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