From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 3 v3] uclibc: fix handling of configuration file
Date: Tue, 29 Jul 2014 23:48:11 +0200 [thread overview]
Message-ID: <20140729234811.425db192@free-electrons.com> (raw)
In-Reply-To: <patchbomb.1405709693@localhost>
Dear Thomas De Schampheleire,
On Fri, 18 Jul 2014 20:54:53 +0200, Thomas De Schampheleire wrote:
> This patch series (part of it poster earlier as RFC) has as main goal to
> fix the uclibc kconfig handling with following requirements in mind:
I've applied the 3 patches of this series, following our discussion,
and after seeing the kconfig-package infra patch series.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-29 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 18:54 [Buildroot] [PATCH 0 of 3 v3] uclibc: fix handling of configuration file Thomas De Schampheleire
2014-07-18 18:54 ` [Buildroot] [PATCH 1 of 3 v3] uclibc: rename SETUP_DOT_CONFIG to FIXUP_DOT_CONFIG Thomas De Schampheleire
2014-07-18 18:54 ` [Buildroot] [PATCH 2 of 3 v3] uclibc: menuconfig: take into account initial settings from config file Thomas De Schampheleire
2014-07-18 18:54 ` [Buildroot] [PATCH 3 of 3 v3] uclibc: update-config: preserve freshly configured settings Thomas De Schampheleire
2014-07-21 20:17 ` Thomas Petazzoni
2014-07-22 11:11 ` Thomas De Schampheleire
2014-07-22 18:24 ` Thomas De Schampheleire
2014-07-26 18:19 ` Thomas De Schampheleire
2014-07-29 21:48 ` Thomas Petazzoni [this message]
2014-07-30 5:21 ` [Buildroot] [PATCH 0 of 3 v3] uclibc: fix handling of configuration file Thomas De Schampheleire
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=20140729234811.425db192@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