From: Darren Hart <dvhart@linux.intel.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: John Stultz <johnstul@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
gthelen@google.com, Dmitry Fink <Dmitry.Fink@palm.com>,
Eric B Munson <ebmunson@us.ibm.com>,
Bruce Ashfield <Bruce.Ashfield@windriver.com>,
Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org,
Richard Tartler <Reinhard.Tartler@informatik.uni-erlangen.de>,
Darren Hart <dvhart@linux.intel.com>
Subject: [PATCH 2/2] merge_config.sh: whitespace cleanup
Date: Mon, 21 Nov 2011 11:42:30 -0800 [thread overview]
Message-ID: <03c7cecf272a4ff0de166ee9dd7b71c920981a31.1321904550.git.dvhart@linux.intel.com> (raw)
In-Reply-To: <1321567131.25715.32.camel@work-vm>
In-Reply-To: <591b0f764fd9eb0bc7873ef775052cb038484ae7.1321904550.git.dvhart@linux.intel.com>
Fix whitespace usage in the clean_up routine.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
---
scripts/kconfig/merge_config.sh | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/kconfig/merge_config.sh b/scripts/kconfig/merge_config.sh
index b91015d..07bb886 100755
--- a/scripts/kconfig/merge_config.sh
+++ b/scripts/kconfig/merge_config.sh
@@ -21,8 +21,8 @@
# See the GNU General Public License for more details.
clean_up() {
- rm -f $TMP_FILE
- exit
+ rm -f $TMP_FILE
+ exit
}
trap clean_up HUP INT TERM
--
1.7.6.4
next prev parent reply other threads:[~2011-11-21 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1321567131.25715.32.camel@work-vm>
2011-11-21 19:42 ` [PATCH 1/2] merge_config.sh: use signal names compatible with dash and bash Darren Hart
2011-11-21 19:42 ` Darren Hart [this message]
2011-11-21 20:14 ` [PATCH 2/2] merge_config.sh: whitespace cleanup John Stultz
2011-11-21 20:05 ` [PATCH 1/2] merge_config.sh: use signal names compatible with dash and bash 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=03c7cecf272a4ff0de166ee9dd7b71c920981a31.1321904550.git.dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=Bruce.Ashfield@windriver.com \
--cc=Dmitry.Fink@palm.com \
--cc=Reinhard.Tartler@informatik.uni-erlangen.de \
--cc=akpm@linux-foundation.org \
--cc=ebmunson@us.ibm.com \
--cc=gthelen@google.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).