public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	rt2400-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Move eeprom drivers to drivers/misc/eeprom
Date: Wed, 21 Jan 2009 10:56:05 +0100	[thread overview]
Message-ID: <20090121105605.018f10d4@hyperion.delvare> (raw)
In-Reply-To: <1232446982-7842-1-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

Hi Wolfram,

On Tue, 20 Jan 2009 11:22:58 +0100, Wolfram Sang wrote:
> As the directory drivers/i2c/chips is going away, we needed a new place
> for the I2C eeprom drivers. After some discussion, the idea of putting
> them into a directory drivers/misc/eeprom was favoured. David Brownell
> added that his SPI eeprom driver could go there as well.
> 
> This patch series carries out the proposal and while at it, moves an
> eeprom driver which was already in drivers/misc to the new location.
> 
> No code inside the drivers was changed and everything was
> succesfully compile-tested.

Thanks a lot for doing this. I've applied all 4 patches.

Things which I think need to be improved on top of your patches:

* Dependencies. The at24 and eeprom drivers should depend on I2C and the
at25 driver should depend on SPI. They did beforehand, thanks to
menu-level dependencies, there's no reason to change this. Should
probably be merged into your patches so that there is no regression.

This might be a good rationale to move the "Misc devices" entry at the
end of the menu, so that users can select the dependencies first.

* Symbol names. At the moment we have:

CONFIG_AT24
CONFIG_SPI_AT25
CONFIG_SENSORS_EEPROM
CONFIG_EEPROM_93CX6

I want to get rid of "SENSORS", at least. But maybe it is the right
time to make the symbol names more consistent? For example:

CONFIG_EEPROM_AT24
CONFIG_EEPROM_AT25
CONFIG_EEPROM_LEGACY
CONFIG_EEPROM_93CX6

This gives some more work on "make oldconfig" but I think it's worth
it. Are there any objections to this change?

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2009-01-21  9:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 10:22 Move eeprom drivers to drivers/misc/eeprom Wolfram Sang
     [not found] ` <1232446982-7842-1-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-01-20 10:22   ` [PATCH 1/4] Move at24 " Wolfram Sang
2009-01-20 10:23   ` [PATCH 2/4] Move old eeprom driver to the new directory /drivers/misc/eeprom Wolfram Sang
2009-01-20 10:23   ` [PATCH 3/4] Move at25-driver (for SPI eeproms) " Wolfram Sang
2009-01-20 10:23   ` [PATCH 4/4] Move 93cx6 eeprom driver " Wolfram Sang
2009-01-21  9:56   ` Jean Delvare [this message]
     [not found]     ` <20090121105605.018f10d4-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-01-21 10:03       ` Move eeprom drivers to drivers/misc/eeprom Wolfram Sang
2009-01-27  7:55   ` David Brownell
     [not found]     ` <200901262355.27913.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2009-01-27  8:04       ` Jean Delvare
     [not found]         ` <20090127090442.35190667-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-01-27  9:53           ` Wolfram Sang
     [not found]             ` <20090127095326.GA8385-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-01-28 12:42               ` 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=20090121105605.018f10d4@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rt2400-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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