public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"H. Peter Anvin" <hpa@linux.kernel.org>,
	"Ingo Molnar" <mingo@elte.hu>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Sachin Sant" <sachinp@in.ibm.com>,
	"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
	"Ian Campbell" <ian.campbell@citrix.com>,
	"Alok Kataria" <akataria@vmware.com>,
	"Jeremy Fitzhardinge" <jeremy@goop.org>,
	"Pasi Kärkkäinen" <pasik@iki.fi>
Subject: Re: [GIT PULL] x86/mm fixes
Date: Thu, 04 Mar 2010 16:03:35 +0100	[thread overview]
Message-ID: <1267715015.25158.203.camel@laptop> (raw)
In-Reply-To: <20100304004425.GA8035@localhost>

On Thu, 2010-03-04 at 08:44 +0800, Wu Fengguang wrote:
> On Thu, Mar 04, 2010 at 01:10:46AM +0800, Linus Torvalds wrote:
> > 
> > 
> > On Wed, 3 Mar 2010, Wu Fengguang wrote:
> > > 
> > > Anyway I just hacked /usr/share/quilt/refresh to automatically run the
> > > kernel style checker:
> > > 
> > > # wfg: check for kernel coding style
> > > if [ -x scripts/checkpatch.pl ]; then
> > >         scripts/checkpatch.pl $patch_file
> > > fi
> > 
> > It's probably sensible to check things, but do remember that some of the 
> > things checkpatch warns about are better left the way they are, rather 
> > than make the code uglier just to make checkpatch happy.
> 
> OK. Here is the simple patch for quilt. I guess it may be hardly
> acceptable for quilt upstream, so only intends to share it here.

I use the below, which allows me to specify what to run on refresh time.

The script I have it use looks like:

$ cat /usr/local/bin/fix-patch.sh
TMP=`tempfile -d /tmp`
awk -f /usr/local/bin/fix-patch.awk $1 > $TMP
if [ -x ./scripts/checkpatch.pl ]; then
        ./scripts/checkpatch.pl $TMP
fi
mv $TMP $1


and fix-patch.awk does things like sanitize mail headers and add
Signed-off-by, lines.

---

--- /usr/share/quilt/refresh~	2008-06-22 00:43:27.000000000 +0200
+++ /usr/share/quilt/refresh	2008-05-28 12:45:27.789068034 +0200
@@ -278,6 +278,10 @@
 
 cat $tmp_patch >> $tmp_result
 
+if [ -n "$QUILT_REFRESH_EXT" ] ; then
+	$QUILT_REFRESH_EXT $tmp_result
+fi
+
 if [ -e $patch_file ] && \
    diff -q $patch_file $tmp_result > /dev/null
 then



  reply	other threads:[~2010-03-04 15:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201003020010.o220Ax3Z025848@hera.kernel.org>
2010-03-02 18:39 ` [GIT PULL] x86/mm fixes Linus Torvalds
2010-03-02 19:09   ` H. Peter Anvin
2010-03-02 19:31   ` H. Peter Anvin
2010-03-03  2:08     ` Wu Fengguang
2010-03-03 17:10       ` Linus Torvalds
2010-03-04  0:44         ` Wu Fengguang
2010-03-04 15:03           ` Peter Zijlstra [this message]
2010-03-05  1:07             ` Wu Fengguang

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=1267715015.25158.203.camel@laptop \
    --to=peterz@infradead.org \
    --cc=akataria@vmware.com \
    --cc=fengguang.wu@intel.com \
    --cc=hpa@linux.kernel.org \
    --cc=hpa@zytor.com \
    --cc=ian.campbell@citrix.com \
    --cc=jeremy@goop.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pasik@iki.fi \
    --cc=sachinp@in.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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