From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Support nested config directories
Date: Thu, 12 May 2016 15:55:54 +0200 [thread overview]
Message-ID: <20160512155554.2add30bd@free-electrons.com> (raw)
In-Reply-To: <1463019163-27543-1-git-send-email-patrick@stwcx.xyz>
Hello,
On Wed, 11 May 2016 21:12:43 -0500, Patrick Williams wrote:
> From: Elizabeth Liner <eliner@us.ibm.com>
>
> Adds an additional recipe to search configs/*/ for defconfig files.
> Recipe added for both $(TOPDIR) and $(BR2_EXTERNAL) to allow nested
> directories for both locations.
>
> Signed-off-by: Elizabeth Liner <eliner@us.ibm.com>
> Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
I believe this would not work well without changes if we were to merge
something like https://patchwork.ozlabs.org/patch/619719/ (which allows
to generate defconfig from fragments).
Could you work with your IBM colleagues to have a solution that works
for both use cases?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-05-12 13:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 15:40 [Buildroot] [PATCH] Adding in support for custom configurations Patrick Williams
2016-04-16 1:06 ` Steve Calfee
2016-04-17 20:31 ` Thomas Petazzoni
2016-04-18 16:25 ` Patrick Williams
2016-04-18 17:07 ` Steve Calfee
2016-04-18 17:14 ` Patrick Williams
2016-04-18 17:37 ` Steve Calfee
2016-04-18 20:59 ` Patrick Williams
2016-04-18 19:15 ` Thomas Petazzoni
2016-04-18 21:44 ` Patrick Williams
2016-04-18 23:57 ` Arnout Vandecappelle
2016-04-19 7:22 ` Thomas Petazzoni
2016-05-12 2:12 ` [Buildroot] [PATCH] Support nested config directories Patrick Williams
2016-05-12 13:55 ` Thomas Petazzoni [this message]
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=20160512155554.2add30bd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.