From: John Stultz <john.stultz@linaro.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
gthelen@google.com, tartler@cs.fau.de,
Dmitry Fink <Dmitry.Fink@palm.com>,
Darren Hart <dvhart@linux.intel.com>,
Eric B Munson <ebmunson@us.ibm.com>,
Bruce Ashfield <Bruce.Ashfield@windriver.com>,
Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org
Subject: [PATCH 0/2] Config fragment tools
Date: Fri, 16 Sep 2011 18:49:17 -0700 [thread overview]
Message-ID: <1316224159-3556-1-git-send-email-john.stultz@linaro.org> (raw)
Last week at Plumbers, Darren Hart and I hosted a BOF on config fragments.
I wanted to say thanks to all the hungry attendees (8pm on the evening where
dinner was fend-for-yourself made it especially hard to draw a crowd) for
their thoughts and discussion.
There I promised to send out some patches to try to get some common tooling
pushed upstream. I realize this isn't difficult code, but after seeing
almost every distro and build system re-implement the same basic
functionality over and over, it seems like there should be some tooling for
this common use case.
I'm sure this tooling won't work for everyone, and I expect it will need to
evolve to adapt for various use cases, but I wanted to push it out so that I
could make concrete what I was describing in the talk, as well as get some
wider feedback.
So let me know if you have any comments or thoughts!
thanks
-john
CC: gthelen@google.com
CC: tartler@cs.fau.de
CC: Dmitry Fink <Dmitry.Fink@palm.com>
CC: Darren Hart <dvhart@linux.intel.com>
CC: Eric B Munson <ebmunson@us.ibm.com>
CC: Bruce Ashfield <Bruce.Ashfield@windriver.com>
CC: Michal Marek <mmarek@suse.cz>
CC: linux-kbuild@vger.kernel.org
John Stultz (2):
kconfig: Add make olddefconfig
kconfig: Add merge_config.sh script
scripts/kconfig/Makefile | 2 +-
scripts/kconfig/conf.c | 4 ++
scripts/kconfig/merge_config.sh | 72 +++++++++++++++++++++++++++++++++++++++
3 files changed, 77 insertions(+), 1 deletions(-)
create mode 100755 scripts/kconfig/merge_config.sh
--
1.7.3.2.146.gca209
next reply other threads:[~2011-09-17 1:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 1:49 John Stultz [this message]
2011-09-17 1:49 ` [PATCH 1/2] kconfig: Add make olddefconfig John Stultz
2011-09-17 6:06 ` Sam Ravnborg
2011-09-19 19:34 ` John Stultz
2011-09-17 1:49 ` [PATCH 2/2] kconfig: Add merge_config.sh script John Stultz
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=1316224159-3556-1-git-send-email-john.stultz@linaro.org \
--to=john.stultz@linaro.org \
--cc=Bruce.Ashfield@windriver.com \
--cc=Dmitry.Fink@palm.com \
--cc=dvhart@linux.intel.com \
--cc=ebmunson@us.ibm.com \
--cc=gthelen@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=tartler@cs.fau.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox