From: Keith Owens <kaos@ocs.com.au>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: include/asm-ppc/platforms/
Date: Wed, 28 Nov 2001 13:35:54 +1100 [thread overview]
Message-ID: <9487.1006914954@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 27 Nov 2001 08:22:44 PDT." <20011127082244.I13091@cpe-24-221-152-185.az.sprintbbd.net>
On Tue, 27 Nov 2001 08:22:44 -0700,
Tom Rini <trini@kernel.crashing.org> wrote:
>I sort of like the include/asm-ppc/platforms symlink idea, but I forget
>if kbuild-2.5 works well with this or if it is/was painful. Keith?
It is only painful it you want to generate files in that directory at
compile time, you have to jump through hoops to prevent the files being
written to the source tree when source and object are seperate
directories. Symlinks for read only files are not a problem.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-28 2:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 11:32 include/asm-ppc/platforms/ Paul Mackerras
2001-11-27 15:22 ` include/asm-ppc/platforms/ Tom Rini
2001-11-27 20:06 ` include/asm-ppc/platforms/ Roman Zippel
2001-11-28 2:35 ` Keith Owens [this message]
2001-12-27 14:59 ` include/asm-ppc/platforms/ Dan Malek
2001-11-27 12:00 ` include/asm-ppc/platforms/ Matt Porter
2001-11-27 15:18 ` include/asm-ppc/platforms/ Geert Uytterhoeven
2001-12-27 15:18 ` include/asm-ppc/platforms/ Dan Malek
2001-11-27 23:44 ` include/asm-ppc/platforms/ Wolfgang Denk
2001-11-28 6:13 ` include/asm-ppc/platforms/ Paul Mackerras
2001-11-28 6:23 ` include/asm-ppc/platforms/ Dan Malek
2001-11-29 11:48 ` include/asm-ppc/platforms/ Paul Mackerras
2001-11-29 15:26 ` include/asm-ppc/platforms/ Tom Rini
2001-11-29 22:19 ` include/asm-ppc/platforms/ Keith Owens
2001-11-29 22:27 ` include/asm-ppc/platforms/ Tom Rini
2001-11-29 22:38 ` include/asm-ppc/platforms/ Keith Owens
2001-11-29 22:46 ` include/asm-ppc/platforms/ Tom Rini
2001-11-29 23:12 ` include/asm-ppc/platforms/ Keith Owens
2001-11-29 23:18 ` include/asm-ppc/platforms/ Tom Rini
2001-11-28 8:46 ` include/asm-ppc/platforms/ Adrian Cox
2001-11-28 21:34 ` include/asm-ppc/platforms/ Paul Mackerras
2001-11-28 21:46 ` include/asm-ppc/platforms/ Adrian Cox
2001-11-29 17:57 ` include/asm-ppc/platforms/ Frank Rowand
2001-11-28 23:50 ` include/asm-ppc/platforms/ Tom Rini
2001-11-29 10:57 ` include/asm-ppc/platforms/ Paul Mackerras
2001-11-28 23:51 ` include/asm-ppc/platforms/ Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2001-11-30 13:30 include/asm-ppc/platforms/ Ralph Blach
2001-11-30 22:08 ` include/asm-ppc/platforms/ Paul Mackerras
2001-11-30 23:22 ` include/asm-ppc/platforms/ Frank Rowand
2001-12-01 3:31 ` include/asm-ppc/platforms/ Dan Malek
2001-12-01 18:19 ` include/asm-ppc/platforms/ Frank Rowand
2001-12-01 22:22 ` include/asm-ppc/platforms/ Dan Malek
2001-12-01 22:41 ` include/asm-ppc/platforms/ Tom Rini
2001-12-01 0:19 ` include/asm-ppc/platforms/ Armin Kuster
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=9487.1006914954@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=trini@kernel.crashing.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).