All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: John Stultz <johnstul@us.ibm.com>
Subject: 
Date: Mon, 26 Sep 2011 20:25:47 -0700	[thread overview]
Message-ID: <1317093949-20219-1-git-send-email-dvhart@linux.intel.com> (raw)
In-Reply-To: <1316582561-23066-1-git-send-email-john.stultz@linaro.org>

Hi John,

I ran into a couple issues dealing with comments in the config fragments and
clean-up after taking a signal. The following patches should address these.

I would still like an option to use allnoconfig for defining truly minimal
configs, but my patches aren't doing quite what I want, so these will have to
follow later. Hopefully tomorrow.

Thanks,

Darren


  parent reply	other threads:[~2011-09-27  3:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21  5:22 [PATCH] kconfig: Add merge_config.sh script John Stultz
2011-09-21  6:44 ` Richard Cochran
2011-09-21 15:18   ` John Stultz
2011-09-21 15:28     ` Darren Hart
2011-09-22 20:05   ` Sam Ravnborg
2011-09-22 20:05     ` Sam Ravnborg
2011-09-21 12:10 ` Michal Marek
2011-09-21 15:36   ` John Stultz
2011-09-21 21:42 ` Dmitry Fink (Palm GBU)
2011-09-22  1:20 ` Dmitry Fink (Palm GBU)
2011-09-22 16:18   ` Arnaud Lacombe
2011-09-27  3:25 ` Darren Hart [this message]
2011-09-27  3:25   ` [PATCH 1/2] merge_config.sh: do not print non-matching lines in the sed expressions Darren Hart
2011-09-27  3:25     ` [PATCH 2/2] merge_config.sh: trap signals and clean up Darren Hart
2011-09-27  3:30     ` [PATCH 1/2] merge_config.sh: do not print non-matching lines in the sed expressions Darren Hart

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=1317093949-20219-1-git-send-email-dvhart@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.