From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Adding in support for custom configurations
Date: Sun, 17 Apr 2016 22:31:43 +0200 [thread overview]
Message-ID: <20160417223143.0b54cce6@free-electrons.com> (raw)
In-Reply-To: <1460734834-32123-1-git-send-email-patrick@stwcx.xyz>
Hello,
On Fri, 15 Apr 2016 10:40:34 -0500, Patrick Williams wrote:
> From: Elizabeth Liner <eliner@us.ibm.com>
>
> This change will add in the custom _defconfig's to the buildroot
> makefile so that when a _defconfig is in the custom directory it is
> recognized correctly, and is able to be used.
>
> Signed-off-by: Elizabeth Liner <eliner@us.ibm.com>
> Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Like Steve replied, I don't see the usefulness for this patch. We
already allow custom configurations to be stored in
$(BR2_EXTERNAL)/configs/.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-17 20:31 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 [this message]
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
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=20160417223143.0b54cce6@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox