mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Daniel Mack <daniel@caiaq.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where to put new sensor drivers?
Date: Fri, 6 Mar 2009 19:55:21 +0100	[thread overview]
Message-ID: <20090306185521.GA1299@ucw.cz> (raw)
In-Reply-To: <20090305150334.GC29699@buzzloop.caiaq.de>

On Thu 2009-03-05 16:03:34, Daniel Mack wrote:
> On Sun, Mar 01, 2009 at 01:41:34PM +0100, Daniel Mack wrote:
> > I wrote a driver for an I2C connected ambient light sensor and submitted
> > it to the linux-i2c list[1]. In the first place, I wasn't aware of
> > drivers/i2c/chips being deprecated and hencei, I subsequently moved it to
> > what seemed to match best in the current tree, drivers/hwmon. But as
> > Jean Delvare pointed out, this is not the place for it either because it
> > doesn't really monitor the hardware, which is true.
> > 
> > So I posted a proposal[2] patch series that adds drivers/sensors for
> > such cases (some of the drivers in the legacy folder drivers/i2c/chips
> > have the same problem than my new one has) but haven't got reply on it
> > yet, probably because linux-i2c is the wrong place to ask.
> 
> Hmm, no feedback here either? I was pointed to the 'industrial I/O'
> thread[1], but that one didn't go mainline yet, and I didn't find any
> reference of someone picking up this idea.

Well drivers/sensors sounds  sane. Or maybe drivers/senses :-). 

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2009-03-06 18:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01 12:41 Daniel Mack
2009-03-05 15:03 ` Daniel Mack
2009-03-06 18:55   ` Pavel Machek [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=20090306185521.GA1299@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=daniel@caiaq.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®