From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/5 v2] core/pkg-kconfig: fix saving back the configuration (branch yem/pr8156)
Date: Sun, 28 Jun 2015 14:30:31 +0200 [thread overview]
Message-ID: <20150628143031.026461ab@free-electrons.com> (raw)
In-Reply-To: <cover.1434213146.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Sat, 13 Jun 2015 18:46:33 +0200, Yann E. MORIN wrote:
> Yann E. MORIN (5):
> core/pkg-kconfig: extract package before using kconfig fragments
> core/pkg-kconfig: ensure kconfig base and fragment files exist
> core/pkg-kconfig: move the kconfig fixups to a macro
> core/pkg-kconfig: run the kconfig fixups after exiting configurators
> core/pkg-kconfig: allow saving config to a non-existing custom config file
All applied, thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-06-28 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 16:46 [Buildroot] [PATCH 0/5 v2] core/pkg-kconfig: fix saving back the configuration (branch yem/pr8156) Yann E. MORIN
2015-06-13 16:46 ` [Buildroot] [PATCH 1/5 v2] core/pkg-kconfig: extract package before using kconfig fragments Yann E. MORIN
2015-06-13 16:46 ` [Buildroot] [PATCH 2/5 v2] core/pkg-kconfig: ensure kconfig base and fragment files exist Yann E. MORIN
2015-06-13 16:46 ` [Buildroot] [PATCH 3/5 v2] core/pkg-kconfig: move the kconfig fixups to a macro Yann E. MORIN
2015-06-13 16:46 ` [Buildroot] [PATCH 4/5 v2] core/pkg-kconfig: run the kconfig fixups after exiting configurators Yann E. MORIN
2015-06-13 16:46 ` [Buildroot] [PATCH 5/5 v2] core/pkg-kconfig: allow saving config to a non-existing custom config file Yann E. MORIN
2015-06-28 12:30 ` 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=20150628143031.026461ab@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