From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Quick guide to Kconfig
Date: Mon, 04 Aug 2014 17:35:17 +0200 [thread overview]
Message-ID: <53DFA835.4000805@redhat.com> (raw)
In-Reply-To: <20140804142742.GF19374@bill-the-cat>
Hi,
On 08/04/2014 04:27 PM, Tom Rini wrote:
> On Fri, Aug 01, 2014 at 01:37:54PM +0900, Masahiro Yamada wrote:
>
> [snip]
>> We had multiple entries in boards.cfg per board
>> (with some differences in the options field)
>> and I generated the correspoing defconfig files.
>>
>> But I guess it would be painful to maintain lots of defconfigs.
>>
>> I expect board maintainers will consolidate defconfigs like you are
>> trying to do, and eventually, we will have one defconfig per board in
>> the future.
>
> So I was thinking about this a bit this morning since I have lots of
> defconfigs I want to merge together as well (see am335x_evm*). I
> suspect the answer is board maintainers will want a README in their
> directory. But today we're inconsistent in a few places. First, it's
> most often board/.../README but we have a few README.somethings (I'm
> guilty there too. And despite 702e601 we have some board-level (I'd
> consider at least) details in docs/ still.
>
> Would board/sunxi/README work for the sunxi cases? Or is that going to
> get too unwieldy?
board/sunxi/README will work fine for sunxi documentation as far as I
can see right now.
Regards,
Hans
next prev parent reply other threads:[~2014-08-04 15:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 4:51 [U-Boot] Quick guide to Kconfig Masahiro Yamada
2014-07-31 6:29 ` Frank Ihle
2014-07-31 6:38 ` Masahiro Yamada
2014-07-31 7:17 ` Frank Ihle
2014-07-31 14:38 ` Hans de Goede
2014-07-31 15:07 ` Ian Campbell
2014-08-01 4:42 ` Masahiro Yamada
2014-08-04 15:49 ` Tom Rini
2014-08-04 15:52 ` Ian Campbell
2014-08-01 4:37 ` Masahiro Yamada
2014-08-04 14:27 ` Tom Rini
2014-08-04 15:35 ` Hans de Goede [this message]
2014-08-05 9:26 ` Ian Campbell
2014-08-05 1:01 ` Masahiro Yamada
2014-08-04 7:12 ` Yan, Miao
2014-08-04 10:19 ` Masahiro Yamada
2014-08-04 10:36 ` Yan, Miao
2014-08-04 11:15 ` Simon Glass
2014-08-04 15:50 ` 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=53DFA835.4000805@redhat.com \
--to=hdegoede@redhat.com \
--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 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.