public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: Michael Hanselmann <linux-kernel@hansmi.ch>,
	linux-kernel@vger.kernel.org, linux-kernel@killerfox.forkbomb.ch,
	johannes@sipsolutions.net, stelian@popies.net,
	chainsaw@gentoo.org
Subject: Re: [RFC] Apple Motion Sensor driver
Date: Mon, 03 Jul 2006 18:52:15 +1000	[thread overview]
Message-ID: <1151916736.19419.40.camel@localhost.localdomain> (raw)
In-Reply-To: <20060703092958.8ca17e53.khali@linux-fr.org>


> I'd rather leave it out for now, and merge it when it has a chance to
> work. Merging non-working code is confusing at best.

:)

> > I want this driver to be included in -mm as soon as possible, to get
> > test feedback and to get it included in 2.6.19 (or maybe 2.6.18? Who
> > knows. ;)). Thus I'd like to get your comments, suggestions, etc. on it.
> 
> 2.6.19 at best.

Oh, it's just a driver update for some powermac specific thingy, so
depending how long 2.6.18 takes, I have no problem as the powermac
maintainer letting that in once it's been properly fixed and reviewed.
(Which I don't have time to do right now neither, but possibly later).

There shouldn't be significant changes to the i2c side of it from
Stelian's driver anyway, more like a new backend using the PMU.

> > +config SENSORS_AMS
> > +	tristate "Motion sensor driver"
> > +	default y
> 
> No, not everyone has this device. We don't have a default for other
> hardware monitoring drivers.
> 
> This should depend on HWMON, and probably EXPERIMENTAL too, until it
> gets some wider testing.
> 
> Also please respect the alphabetical order.

It can stay default y as lons as it depends on PPC_PMAC (which it should
do anyway)

> If you are going to have many source files and a composite module,
> please create your own subdirectory under drivers/hwmon and put all
> your stuff here. The kernel build system is notoriously bad at handling
> multiple composite modules within the same subdirectory.

Agreed.

Cheers,
Ben.



  reply	other threads:[~2006-07-03  8:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-02 22:26 [RFC] Apple Motion Sensor driver Michael Hanselmann
2006-07-03  2:33 ` Dmitry Torokhov
2006-07-03  3:14 ` Andrew Morton
2006-07-03  3:47   ` Benjamin Herrenschmidt
2006-07-03  4:00     ` Andrew Morton
2006-07-03  6:56   ` Michael Hanselmann
2006-07-03  9:02     ` Stelian Pop
2006-07-03  7:29 ` Jean Delvare
2006-07-03  8:52   ` Benjamin Herrenschmidt [this message]
2006-07-03 10:12 ` Stelian Pop
2006-07-03 10:19   ` Johannes Berg
2006-07-03 10:45   ` Michael Hanselmann
2006-07-03 10:49     ` Benjamin Herrenschmidt
2006-07-03 11:31       ` Stelian Pop
2006-07-03 13:16         ` Dmitry Torokhov
2006-07-03 13:25     ` Stefan Richter
2006-07-03 13:44 ` Dmitry Torokhov
2006-07-03 22:45 ` Michael Hanselmann
2006-07-04 16:45   ` Michael Buesch

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=1151916736.19419.40.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=chainsaw@gentoo.org \
    --cc=johannes@sipsolutions.net \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@hansmi.ch \
    --cc=linux-kernel@killerfox.forkbomb.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stelian@popies.net \
    /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