public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@hansmi.ch, linux-kernel@vger.kernel.org,
	lm-sensors@lm-sensors.org, khali@linux-fr.org,
	linux-kernel@killerfox.forkbomb.ch, johannes@sipsolutions.net,
	stelian@popies.net, chainsaw@gentoo.org
Subject: Re: [RFC] Apple Motion Sensor driver
Date: Sun, 2 Jul 2006 21:00:34 -0700	[thread overview]
Message-ID: <20060702210034.8abeb4d5.akpm@osdl.org> (raw)
In-Reply-To: <1151898448.19419.32.camel@localhost.localdomain>

On Mon, 03 Jul 2006 13:47:28 +1000
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:

> On Sun, 2006-07-02 at 20:14 -0700, Andrew Morton wrote:
> > On Mon, 3 Jul 2006 00:26:49 +0200
> > Michael Hanselmann <linux-kernel@hansmi.ch> wrote:
> > 
> > > Below you find the latest revision of my AMS driver.
> > 
> > I was about to merge the below, then this comes along.  Now what?
> 
> Michael's driver is a new version that adds support for non-i2c (PMU
> based) chips found on new machines. It would be nice to have it, though
> it definitely needs a bit of review from Stelian, the original author.
> 
> What I would suggest at this point is to merge Stelian's original
> driver, as you were about todo, then have Michael produce a patch
> against it to be reviewed that could then be merged later on. I'm fine
> having that "later on" still be in the 2.6.18 timeframe since we aren't
> talking about anything critical here, just a fairly minor driver update
> that is nice to have, but we can decide that later based on the reviews
> of Michael's changes).

Yes, but it wouldn't be a "patch against it" - Michael's patch adds
multiple files with different names.  So it would be a revert-and-redo.


  reply	other threads:[~2006-07-03  4:01 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 [this message]
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
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=20060702210034.8abeb4d5.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=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=lm-sensors@lm-sensors.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