From: dsilvers@simtec.co.uk (Daniel Silverstone)
To: linux-arm-kernel@lists.infradead.org
Subject: Default machine include placements
Date: Mon, 25 Jan 2010 10:49:59 +0000 [thread overview]
Message-ID: <20100125104959.GC5772@digital-scurf.org> (raw)
In-Reply-To: <20100125104425.GO26562@trinity.fluff.org>
On Mon, Jan 25, 2010 at 10:44:25AM +0000, Ben Dooks wrote:
> We do a bit of #include <plat/xxx-base.h> already for some things.
> The 'empty' headers always seme to end up catching more copyright
> statement than the space they end up saving.
I guess it depends if you're aiming for space savings or "only one place to fix
a bug" in that case.
> Not sure how git deals with symlinks, and I think this will just leave
> us a mess on systems that don't really understand symlinks.
Does the kernel even build on systems which don't properly support symbolic
links? I thought we had more problems with caseless filesystems anyway?
Regards,
Daniel.
--
Daniel Silverstone http://www.simtec.co.uk/
next prev parent reply other threads:[~2010-01-25 10:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 4:02 Default machine include placements Ben Dooks
2010-01-25 4:02 ` Ben Dooks
2010-01-25 10:05 ` Russell King - ARM Linux
2010-01-25 10:05 ` Russell King - ARM Linux
2010-01-25 10:28 ` Ben Dooks
2010-01-25 10:28 ` Ben Dooks
2010-01-25 10:32 ` Daniel Silverstone
2010-01-25 10:44 ` Ben Dooks
2010-01-25 10:49 ` Daniel Silverstone [this message]
2010-01-25 10:55 ` Ben Dooks
2010-01-25 11:19 ` Russell King - ARM Linux
2010-01-25 11:53 ` Ben Dooks
2010-01-25 12:04 ` Russell King - ARM Linux
2010-01-25 13:54 ` Ben Dooks
2010-01-25 14:59 ` Russell King - ARM Linux
2010-01-25 21:48 ` Ben Dooks
2010-01-25 14:03 ` Ben Dooks
2010-01-25 10:57 ` Mark Brown
2010-01-25 10:49 ` Ben Dooks
2010-01-25 10:49 ` Ben Dooks
2010-01-25 11:01 ` Russell King - ARM Linux
2010-01-25 11:01 ` Russell King - ARM Linux
2010-01-25 11:44 ` Ben Dooks
2010-01-25 11:44 ` Ben Dooks
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=20100125104959.GC5772@digital-scurf.org \
--to=dsilvers@simtec.co.uk \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.