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: Grant Likely
	<grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>,
	Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: New home for DS1682 driver
Date: Wed, 7 Oct 2009 12:07:34 +0200	[thread overview]
Message-ID: <20091007120734.31a41f33@hyperion.delvare> (raw)
In-Reply-To: <20091007095610.GF3177-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

On Wed, 7 Oct 2009 11:56:10 +0200, Wolfram Sang wrote:
> On Wed, Oct 07, 2009 at 11:50:17AM +0200, Jean Delvare wrote:
> > Hi Grant,
> > 
> > Driver ds1682 needs a new home, as drivers/i2c/chips will be gone soon.
> > Do you have a preference for where it should go?
> > 
> > As the device includes an EEPROM, the driver could go in
> > drivers/misc/eeprom, but OTOH the EEPROM in question is so small that
> > this can hardly be considered the main feature of the driver. So maybe
> > just drivers/misc?
> 
> I would much prefer drivers/misc.

OK, fine with me. Will you send a patch?

> What about tsl2550.c? I thought the plan back
> then was to wait for IIO becoming mainline? Or shall we also put it to
> drivers/misc until then?

For tsl2550, the plan is indeed to wait for iio to become mainline. Or
the alternative ALS subsystem. I hope we won't have to wait too long.

-- 
Jean Delvare

  parent reply	other threads:[~2009-10-07 10:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07  9:50 New home for DS1682 driver Jean Delvare
     [not found] ` <20091007115017.6941faa7-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-10-07  9:56   ` Wolfram Sang
     [not found]     ` <20091007095610.GF3177-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-10-07 10:07       ` Jean Delvare [this message]
     [not found]         ` <20091007120734.31a41f33-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-10-07 10:25           ` Wolfram Sang
     [not found]             ` <20091007102557.GG3177-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-10-07 12:12               ` Jonathan Cameron
     [not found]                 ` <4ACC85B7.2010300-KWPb1pKIrIJaa/9Udqfwiw@public.gmane.org>
2009-10-07 12:27                   ` Jean Delvare
     [not found]                     ` <20091007142746.4bc4f0f4-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-10-07 12:47                       ` Wolfram Sang
     [not found]                         ` <20091007124748.GH3177-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-10-07 15:11                           ` Jonathan Cameron
2009-10-07 13:03                       ` Rodolfo Giometti
2009-10-07 13:48   ` Grant Likely
2009-10-07 22:31   ` [PATCH] i2c/chips: move ds1682 to drivers/misc Wolfram Sang
     [not found]     ` <1254954710-18263-1-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-10-07 22:34       ` Grant Likely
2009-10-08  6:40       ` Jean Delvare
     [not found]         ` <20091008084041.597e4c6d-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-10-08  9:30           ` Wolfram Sang

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=20091007120734.31a41f33@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@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