From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Julia Lawall" <julia@diku.dk>,
"Pekka Enberg" <penberg@kernel.org>,
"Américo Wang" <xiyou.wangcong@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Jonathan Corbet" <corbet@lwn.net>,
LKML <linux-kernel@vger.kernel.org>,
"Andy Whitcroft" <apw@shadowen.org>,
"Dave Jones" <davej@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Nicolas Palix" <npalix@diku.dk>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH] checkpatch: Test for kmalloc/memset(0) pairs
Date: Sun, 20 Mar 2011 15:48:27 +0100 [thread overview]
Message-ID: <20110320154827.7ba3358b@varda> (raw)
In-Reply-To: <20110320105412.GA11266@elte.hu>
El Sun, 20 Mar 2011 11:54:12 +0100
Ingo Molnar <mingo@elte.hu> escribió:
>
> I think the point Pekka tried to make is to have it integrated into the kbuild
> mechanism as well at a certain point. That way it's very easy to use it and we
> maintainers could require frequent patch submitters to use those tools to check
> the quality of their patches. Right now i cannot require that, as it's not part
> of the kernel repo. Requiring a checkpatch.pl check is much easier, as it's
> available to everyone who is writing kernel patches.
But a perl interpreter is not shipped with the kernel, is it? neither a
posix shell or a python interpreter ...
The scripts are already shipped with the kernel, the "interpreter" have
to be installed in the dev machine like you have to install perl, make,
gcc, etc
just my two cents as a bystander :)
>
> Thanks,
>
> Ingo
> --
next prev parent reply other threads:[~2011-03-20 14:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 2:52 [PATCH] checkpatch: Test for kmalloc/memset(0) pairs Steven Rostedt
2011-03-18 3:15 ` Jonathan Corbet
2011-03-18 3:32 ` Steven Rostedt
2011-03-20 3:40 ` Américo Wang
2011-03-20 7:02 ` Pekka Enberg
2011-03-20 8:01 ` Julia Lawall
2011-03-20 9:02 ` Pekka Enberg
2011-03-20 9:17 ` Julia Lawall
2011-03-20 10:54 ` Ingo Molnar
2011-03-20 11:06 ` Pekka Enberg
2011-03-20 11:32 ` Nicolas Palix
2011-03-20 12:00 ` Julia Lawall
2011-03-20 11:09 ` Alexey Dobriyan
2011-03-20 12:38 ` Julia Lawall
2011-03-20 14:48 ` Alejandro Riveira Fernández [this message]
2011-03-21 13:13 ` Steven Rostedt
2011-03-24 15:34 ` Aneesh Kumar K. V
2011-03-24 16:08 ` Julia Lawall
2011-03-24 16:10 ` Nicolas Palix
2011-03-24 18:30 ` Arnaud Lacombe
2011-03-24 20:39 ` Julia Lawall
2011-03-24 17:28 ` Aneesh Kumar K. V
2011-03-19 19:39 ` Dave Jones
2011-03-21 13:26 ` Steven Rostedt
2011-03-21 13:29 ` Steven Rostedt
2011-03-21 13:55 ` Borislav Petkov
2011-03-22 19:58 ` checkpatch: introduce --nocs to disable CodingStyle warnings Dave Jones
2011-03-22 20:21 ` Joe Perches
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=20110320154827.7ba3358b@varda \
--to=ariveira@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=corbet@lwn.net \
--cc=davej@redhat.com \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npalix@diku.dk \
--cc=penberg@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=xiyou.wangcong@gmail.com \
/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).