From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] header files in include/ versus arch/<arch>/include/asm/?
Date: Sun, 20 Dec 2015 07:46:40 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.20.1512200735550.22527@localhost> (raw)
working on MPC8360-based project and noticed that what appears to be
a powerpc-specific header file (include/fsl_immap.h) is in the
top-level include/ directory, as opposed to where i would have
expected it (arch/powerpc/include/asm/).
it's not the only one ... there appear to be others. what is the
rationale for installing a header file if it *appears* to be
architecture-specific? it seems like there's a fair bit of freescale
powerpc content under include/, but maybe i'm just misreading this.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
reply other threads:[~2015-12-20 12:46 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=alpine.LFD.2.20.1512200735550.22527@localhost \
--to=rpjday@crashcourse.ca \
--cc=u-boot@lists.denx.de \
/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