public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stelian Pop <stelian@popies.net>
To: Michael Hanselmann <linux-kernel@hansmi.ch>
Cc: Andrew Morton <akpm@osdl.org>,
	Dmitry Torokhov <dtor_core@ameritech.net>,
	"Aristeu S. Rozanski F." <aris@cathedrallabs.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>, Robert Love <rml@novell.com>,
	Jean Delvare <khali@linux-fr.org>,
	Rene Nussbaumer <linux-kernel@killerfox.forkbomb.ch>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	nicolas@boichat.ch
Subject: Re: [PATCH] Apple Motion Sensor driver
Date: Sat, 11 Nov 2006 23:00:17 +0100	[thread overview]
Message-ID: <1163282417.32084.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20061111214143.GA25609@hansmi.ch>

Le samedi 11 novembre 2006 à 22:41 +0100, Michael Hanselmann a écrit :
> On Sat, Nov 11, 2006 at 10:36:11PM +0100, Stelian Pop wrote:
> > This driver adds support for the Apple Motion Sensor (AMS) as found in 2005
> > revisions of Apple PowerBooks and iBooks.  It implements both the PMU and
> > I²C variants.
> 
> I've modified my driver to use an accelerometer class. 

Hmmm, I didn't know such a thing existed.

> Do you want the code?

Just make sure it gets submitted upstream so it gets no lost.

I don't have a particular use for the accelerometer myself, I was just
digging thru the pile of my local patches and I noticed that all the
work (mine, yours and others) on the ams device seemed on its way to be
lost, since nobody picked up the patch.

But if you're still actively working on it and plan to submit it later,
that's perfectly ok with me.

Stelian.
-- 
Stelian Pop <stelian@popies.net>


  reply	other threads:[~2006-11-11 22:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 21:36 [PATCH] Apple Motion Sensor driver Stelian Pop
2006-11-11 21:41 ` Michael Hanselmann
2006-11-11 22:00   ` Stelian Pop [this message]
2006-11-12  8:37     ` Michael Hanselmann
2006-11-12 21:38       ` Stelian Pop
2006-11-13 18:11         ` Jean Delvare
2006-11-13 18:18           ` Dmitry Torokhov
2006-11-13 15:04 ` Dmitry Torokhov
2006-11-13 15:29   ` Stelian Pop
2006-11-13 15:53     ` Dmitry Torokhov
2006-11-13 16:14       ` Stelian Pop
2006-11-13 16:20         ` Johannes Berg
2006-11-13 18:14           ` Jean Delvare
2006-11-13 18:18             ` Johannes Berg
2006-11-13 18:24               ` Michael Hanselmann
2006-11-13 20:55               ` Stelian Pop
2006-11-13 18:20         ` Dmitry Torokhov
2006-11-13 18:55           ` Robert Love
2006-11-13 20:52           ` Stelian Pop
2006-11-13 21:23             ` Johannes Berg
2006-11-13 21:39               ` Stelian Pop
2006-11-13 18:06 ` Jean Delvare
2006-11-13 18:23   ` Henrique de Moraes Holschuh
2006-11-13 20:41   ` Stelian Pop
2006-11-14  3:09     ` Henrique de Moraes Holschuh

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=1163282417.32084.18.camel@localhost.localdomain \
    --to=stelian@popies.net \
    --cc=akpm@osdl.org \
    --cc=aris@cathedrallabs.org \
    --cc=benh@kernel.crashing.org \
    --cc=dtor_core@ameritech.net \
    --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=nicolas@boichat.ch \
    --cc=paulus@samba.org \
    --cc=rml@novell.com \
    /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