From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Takashi Iwai" <tiwai@suse.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
"Éric Piel" <Eric.Piel@tremplin-utc.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] [PATCH v2] lis3: Fix Oops with NULL platform data
Date: Fri, 24 Sep 2010 16:10:06 +0100 [thread overview]
Message-ID: <4C9CBF4E.7080200@cam.ac.uk> (raw)
In-Reply-To: <20100924163005.7704f63e@endymion.delvare>
On 09/24/10 15:30, Jean Delvare wrote:
> On Fri, 24 Sep 2010 16:14:26 +0200, Takashi Iwai wrote:
>> At Fri, 24 Sep 2010 06:58:02 -0700,
>> Guenter Roeck wrote:
>>>
>>> On Thu, Sep 23, 2010 at 01:58:33AM -0400, Takashi Iwai wrote:
>>>> The recent addition of threaded irq handler causes a NULL dereference
>>>> when used with hp_accel driver, which has NULL pdata.
>>>>
>>>> Acked-by: Samu Onkalo <samu.p.onkalo@nokia.com>
>>>> Acked-by: Acked-by: Guenter Roeck <guenter.roeck@ericsson.com>
>>>> Cc: <stable@kernel.org>
>>>> Signed-off-by: Takashi Iwai <tiwai@suse.de>
>>>
>>> Applied.
>>
>> Oh, does this driver belong to hwmon tree?
>> Jean told me that this isn't managed in hwmon, so I had an impression
>> that it's an orphan driver.
>
> Well, as long as the driver lives in drivers/hwmon and the hwmon
> subsystem is maintained, it seems fair to consider the driver
> maintained.
Technically hwmon is orphan (according to MAINTAINERS.) But that's not to
say that various people aren't looking after various parts of it and
I believe Andrew Morton is acting as maintainer of last resort.
>
> That being said, I indeed would like all non-hwmon drivers to go away
> from drivers/hwmon. Originally we were waiting for iio to settle first,
> but apparently this is taking forever.
More developers and code reviewers always welcome!
> The 4 drivers I would like to
> kick are: ams, hdaps, lis3lv02d and applesmc. They are primarily
> accelerometer device drivers. Not sure where to put them,
> drivers/accel(erometer), drivers/misc, drivers/misc/accel(erometer),
> drivers/input/accel(erometer)... Opinions welcome.
If the primary use is as an input device then talk to Dmitry. Some
accelerometers are being taken into input. There are some open questions
on naming etc currently being debated so anyone interested should get
involved in those asap.
Jonathan
next prev parent reply other threads:[~2010-09-24 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 5:58 [PATCH v2] lis3: Fix Oops with NULL platform data Takashi Iwai
2010-09-24 13:58 ` Guenter Roeck
2010-09-24 14:14 ` Takashi Iwai
2010-09-24 14:30 ` [lm-sensors] " Jean Delvare
2010-09-24 15:10 ` Jonathan Cameron [this message]
2010-09-24 15:17 ` Guenter Roeck
2010-09-24 17:07 ` Jonathan Cameron
2010-09-25 11:11 ` Jean Delvare
2010-09-25 11:01 ` Jean Delvare
2010-09-25 13:47 ` Jonathan Cameron
2010-09-24 15:16 ` Guenter Roeck
2010-09-24 15:22 ` Éric Piel
2010-09-24 17:14 ` Jonathan Cameron
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=4C9CBF4E.7080200@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Eric.Piel@tremplin-utc.net \
--cc=akpm@linux-foundation.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=tiwai@suse.de \
/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