From: Robert P. J. Day <rpjday@crashcourse.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot] what is the *recommended* split between defconfig file and header file?
Date: Wed, 20 Jul 2016 04:56:18 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1607200453450.25086@localhost.localdomain> (raw)
In-Reply-To: <20160719192412.GK7260@bill-the-cat>
On Tue, 19 Jul 2016, Tom Rini wrote:
> On Tue, Jul 19, 2016 at 04:15:47AM -0400, Robert P. J. Day wrote:
>
> >
> > kind of a style question but what is the preferred way to define a
> > board in the sense of what belongs in the defconfig file and what
> > belongs in the header file?
>
> The header files will eventually go away. Most of the contents are
> things that could be, but haven't yet been, converted. A few things
> like default environment are going to be harder to figure out.
and what about the advantage of header files that allow the
inclusion of other header files to reduce duplication? will config
files be extended to allow the same thing? (they don't do that now, do
they?)
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2016-07-20 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 8:15 [U-Boot] what is the *recommended* split between defconfig file and header file? Robert P. J. Day
2016-07-19 19:24 ` Tom Rini
2016-07-20 8:56 ` Robert P. J. Day [this message]
2016-07-20 10:21 ` Andreas Färber
2016-07-20 12:20 ` Tom Rini
2016-07-21 11:24 ` Robert P. J. Day
2016-07-21 14:44 ` Tom Rini
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.1607200453450.25086@localhost.localdomain \
--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