From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Len Brown <lenb@kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Len Brown <len.brown@intel.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
x86@kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [RFC PATCH] x86: create drivers/x86/ from drivers/misc/
Date: Fri, 28 Nov 2008 22:16:47 -0200 [thread overview]
Message-ID: <20081129001647.GA8699@khazad-dum.debian.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0811281801520.24773@localhost.localdomain>
On Fri, 28 Nov 2008, Len Brown wrote:
> > > Move x86 platform specific drivers from drivers/misc/
> > > to a new home under drivers/x86/.
[...]
> > We already have 81 one directory entries under drivers/
> > and with patch you open up for an additional
> > directory for each arch - not elegant.
>
> I followed the example of drivers/s390/,
> per Linus' suggestion.
>
> The other place that seemed to suggest itself was
> arch/x86/drivers/, as we already have:
>
> arch/um/drivers/
> arch/sh/drivers/
> arch/cris/*/drivers/
IMHO, from a purely "tree organization" point of view, it would be best if
arch-specific platform drivers were under drivers/platform/<arch>/. And
arch/ be left for the core arch-specific stuff.
Whether that would work well, when arch maintenance factors are taken into
account, I don't know.
> > As it is today (before this patch) the directories unider
> > drivers/ said what the drivers was used for - which is logical.
> >
> > But with this new arch specific directory it is no longer obvious
> > is a driver should be located under say drivers/net/* or
> > drivers/arm/* in case it is a arm specific driver.
drivers/platform/<arch> would help in that regard, I think.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2008-11-29 0:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081128213620.2ec593d4.sfr@canb.auug.org.au>
[not found] ` <4930307C.30106@oracle.com>
[not found] ` <20081129083550.3c23af37.sfr@canb.auug.org.au>
[not found] ` <alpine.LFD.2.00.0811281649001.24773@localhost.localdomain>
[not found] ` <alpine.LFD.2.00.0811281702570.24773@localhost.localdomain>
2008-11-28 22:09 ` [RFC PATCH] x86: create drivers/x86/ from drivers/misc/ Len Brown
2008-11-28 22:35 ` Sam Ravnborg
2008-11-28 23:16 ` Len Brown
2008-11-29 0:16 ` Henrique de Moraes Holschuh [this message]
2008-12-01 4:35 ` Len Brown
2008-11-29 1:00 ` Randy Dunlap
2008-11-29 7:23 ` Sam Ravnborg
2008-11-29 7:38 ` Sam Ravnborg
2008-12-01 5:00 ` Len Brown
2008-12-01 5:54 ` Sam Ravnborg
2008-12-01 6:02 ` [RFC PATCH v2] create drivers/platform/x86/ " Len Brown
2008-12-01 6:03 ` [PATCH 1/2] drivers/misc/Makefile, Kconfig: cleanup Len Brown
2008-12-01 7:41 ` Sam Ravnborg
2008-12-01 19:23 ` Len Brown
2008-12-01 6:05 ` [PATCH 2/2] create drivers/platform/x86/ from drivers/misc/ Len Brown
2008-12-01 7:48 ` [RFC PATCH v2] " Ingo Molnar
2008-12-01 19:12 ` Len Brown
2008-11-28 23:20 ` [RFC PATCH] x86: create drivers/x86/ " Len Brown
2008-12-01 4:49 ` Randy Dunlap
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=20081129001647.GA8699@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
--cc=x86@kernel.org \
/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