From: Andrey Volkov <avolkov@varma-el.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Greg KH <gregkh@suse.de>, Jamey Hicks <jamey.hicks@hp.com>,
linux-kernel@vger.kernel.org, rpurdie@rpsys.net,
tony.luck@intel.com, edwardsg@sgi.com
Subject: Re: [Linux-fbdev-devel] Re: Where is place of arch independed companion chips?
Date: Wed, 03 Aug 2005 13:09:10 +0400 [thread overview]
Message-ID: <42F089B6.8000304@varma-el.com> (raw)
In-Reply-To: <1123019379.7782.86.camel@localhost.localdomain>
Richard Purdie wrote:
> On Mon, 2005-08-01 at 11:13 -0700, Greg KH wrote:
>
>>>Good question. I was about to submit a patch that created
>>>drivers/platform because the toplevel driver for MQ11xx is a
>>>platform_device driver. Any thoughts on this?
>>
>>drivers/platform sounds good to me.
>
>
> In another thread (about the ucb1x00) we came up with the idea of
> drivers/mfd (mfd = multi function devices).
>
> The core and platform specific parts would live here with suitable clear
> naming and the subsection specific parts that were separable would live
> in the appropriate place within the kernel.
>
> Just another idea to add to the mix and removes the dilemma of a
> multifunction device with isn't platform based...
>
drivers/mfd as drivers/mfd, I have not objections. Who will send the
patch first?
--
Regards
Andrey Volkov
P.S. Tony, Greg, may be it will someone from you? (I've in mind sn/ subdir)
next prev parent reply other threads:[~2005-08-03 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 11:52 Where is place of arch independed companion chips? Andrey Volkov
2005-07-31 4:40 ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-07-31 12:21 ` Andrey Volkov
2005-08-01 12:29 ` Jamey Hicks
2005-08-01 18:13 ` Greg KH
2005-08-01 18:38 ` Andrey Volkov
2005-08-02 21:49 ` Richard Purdie
2005-08-03 9:09 ` Andrey Volkov [this message]
2005-08-08 21:09 ` Mark Underwood
2005-08-03 6:17 ` Pavel Machek
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=42F089B6.8000304@varma-el.com \
--to=avolkov@varma-el.com \
--cc=edwardsg@sgi.com \
--cc=gregkh@suse.de \
--cc=jamey.hicks@hp.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=tony.luck@intel.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