From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc64-dev@ozlabs•org
Cc: linuxppc-dev@ozlabs•org, Tom Rini <trini@kernel•crashing.org>,
Stephen Rothwell <sfr@canb•auug.org.au>
Subject: Re: [PATCH 3/3] Move all the very similar files
Date: Wed, 24 Aug 2005 22:03:26 +0200 [thread overview]
Message-ID: <200508242203.27210.arnd@arndb.de> (raw)
In-Reply-To: <20050824182020.GB15735@smtp.west.cox.net>
On Middeweken 24 August 2005 20:20, Tom Rini wrote:
> On Tue, Aug 23, 2005 at 12:05:36PM -0500, Kumar Gala wrote:
> >
> > This seems reasonable then to have them in include/asm-powerpc. I
>
> No it doesn't. You can easily make the drivers get the includes from
> <platforms/pmac/foo.h>, arch/$(ARCH) is already always in the search
> path, I believe (if not, it's easy to add Makefile things to get it).
I don't think any architecture except ppc32 has traditionally had
arch/$ARCH in its include path, and it would probably come as a surprise
to many kernel developers if this were used more.
Currently, there seem to be hardly any users of this "feature" in ppc32
that can't be trivially converted to including local files, so I'd
rather not see this moved over to arch/powerpc.
Arnd <><
next prev parent reply other threads:[~2005-08-24 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050822141235.GA7110@austin.ibm.com>
2005-08-22 14:20 ` [PATCH 3/3] Move all the very similar files Kumar Gala
2005-08-22 15:01 ` Olof Johansson
2005-08-23 5:41 ` Benjamin Herrenschmidt
2005-08-23 7:31 ` Stephen Rothwell
2005-08-23 17:05 ` Kumar Gala
2005-08-24 18:20 ` Tom Rini
2005-08-24 20:03 ` Arnd Bergmann [this message]
2005-08-24 20:13 ` Tom Rini
2005-08-24 20:44 ` Brad Boyer
2005-08-22 6:02 [PATCH 1/3] Create include/asm-powerpc Stephen Rothwell
2005-08-22 6:05 ` [PATCH 2/3] Move the identical files from include/asm-ppc{,64} Stephen Rothwell
2005-08-22 6:10 ` [PATCH 3/3] Move all the very similar files Stephen Rothwell
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=200508242203.27210.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=linuxppc64-dev@ozlabs$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=trini@kernel$(echo .)crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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