From: Paul Mackerras <paulus@samba.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: moving include/asm-ppc/platforms
Date: Mon, 17 Dec 2001 22:28:36 +1100 (EST) [thread overview]
Message-ID: <15389.55012.312836.197493@argo.ozlabs.ibm.com> (raw)
With the addition of -I$(TOPDIR)/arch/$(ARCH) to the compilation flags
for the kernel, we can now move the platform-specific header files
from include/asm-ppc/platforms to arch/ppc/platforms, which is where I
think they belong. That does require changing <asm/platforms/blah.h>
to <platforms/blah.h>, but that is not a big job because these headers
tend to get included in only a few places.
For 2.4 we will keep the ugly lists of ifdefs in places like serial.h
and mpc8xx.h. For 2.5 we should change over to using a mechanism to
copy an appropriate platform-dependent file to arch/ppc/platform.h.
Once we have moved include/asm-ppc/platforms/*.h to arch/ppc/platforms,
it will just about be time to do a big merge from devel into
linuxppc_2_4 and thence to Marcelo's tree.
Paul.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-12-17 11:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=15389.55012.312836.197493@argo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).