From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
roel <12o3l@tiscali.nl>, lkml <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@xenotime.net>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] spin_lock_unlocked cleanups
Date: Fri, 28 Sep 2007 11:06:09 +0200 [thread overview]
Message-ID: <1190970369.18681.17.camel@chaos> (raw)
In-Reply-To: <20070928085632.GC12086@shadowen.org>
On Fri, 2007-09-28 at 09:56 +0100, Andy Whitcroft wrote:
> > > I think we're ready to wire checkpatch up to a email robot which monitors
> > > the mailing lists and sends people nastygrams. I bet that'll be popular ;)
> >
> > We should wire it up to git-commit as well. A lot of that comes in via
> > git subsystems.
>
> The problem with git-commit is who's repo to add the hook to. I did
> attempt to do this by picking up each of linus' main releases and then
> using the git blame engine to attribute each "failure" to a particular
> commit. The plan then would be to send a nasty-gram to the committer
> about violations there-in.
>
> I'll try and find some time to get this bit polished and at least
> emailing me.
The question is, whether we can convince the git developers to integrate
it. When a commit happens and checkpatch.pl is in scripts/, then run the
patch through it before doing the actual commit.
tglx
next prev parent reply other threads:[~2007-09-28 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 21:36 [PATCH] spin_lock_unlocked cleanups roel
2007-09-28 8:17 ` Thomas Gleixner
2007-09-28 8:26 ` Andrew Morton
2007-09-28 8:30 ` Ingo Molnar
2007-09-28 8:55 ` Andrew Morton
2007-09-28 8:32 ` Thomas Gleixner
2007-09-28 8:56 ` Andy Whitcroft
2007-09-28 9:06 ` Thomas Gleixner [this message]
2007-09-28 21:15 ` Sean
2007-09-28 8:53 ` Andy Whitcroft
2007-09-28 9:05 ` Andrew Morton
2007-09-28 17:31 ` Mark Gross
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=1190970369.18681.17.camel@chaos \
--to=tglx@linutronix.de \
--cc=12o3l@tiscali.nl \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rdunlap@xenotime.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