From: Jamey Hicks <jamey.hicks@hp.com>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, jamey@handhelds.org,
anpaza@mail.ru, rmk@arm.linux.org.uk
Subject: Re: platform-device-driver-for-mq11xx-graphics-chip.patch added to -mm tree
Date: Fri, 05 Aug 2005 08:29:30 -0400 [thread overview]
Message-ID: <42F35BAA.1070506@hp.com> (raw)
In-Reply-To: <1123228133.7649.4.camel@localhost.localdomain>
Richard Purdie wrote:
>On Fri, 2005-08-05 at 00:18 -0700, akpm@osdl.org wrote:
>
>
>>The patch titled
>>
>> platform-device driver for MQ11xx graphics chip
>>
>>has been added to the -mm tree. Its filename is
>>
>> platform-device-driver-for-mq11xx-graphics-chip.patch
>>
>> drivers/platform/.tmp_versions/mq11xx_base.mod | 2
>>
>>
>
>I doubt that should be there...
>
>
>
>> drivers/platform/Kconfig | 23
>> drivers/platform/Makefile | 5
>> drivers/platform/mq11xx.h | 925 ++++++++++++++++
>> drivers/platform/mq11xx_base.c | 1390 +++++++++++++++++++++++++
>>
>>
>
>I'm also still wondering if drivers/mfd would be better in the long term
>for code like this (as mentioned in various threads on LKML). That way
>it is doesn't have to be platform device specific...
>
>
>
I do not have a problem with moving these drivers to drivers/mfd. I do
want to have a policy that says where such drivers should go.
Jamey
next prev parent reply other threads:[~2005-08-05 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200508050719.j757J9KO032652@shell0.pdx.osdl.net>
2005-08-05 7:48 ` platform-device-driver-for-mq11xx-graphics-chip.patch added to -mm tree Richard Purdie
2005-08-05 7:59 ` Andrew Morton
2005-08-05 12:29 ` Jamey Hicks [this message]
2005-08-08 18:52 ` Russell King
2005-08-08 20:25 ` Jamey Hicks
2005-08-05 13:43 ` Alexey Dobriyan
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=42F35BAA.1070506@hp.com \
--to=jamey.hicks@hp.com \
--cc=akpm@osdl.org \
--cc=anpaza@mail.ru \
--cc=jamey@handhelds.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=rpurdie@rpsys.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