From: Willy Tarreau <w@1wt.eu>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: davej@redhat.com, jschopp@austin.ibm.com, apw@uk.ibm.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: scripts/checkpatch.pl in 2.4 git
Date: Sat, 3 Jan 2009 15:50:24 +0100 [thread overview]
Message-ID: <20090103145024.GB21058@1wt.eu> (raw)
In-Reply-To: <3f9a31f40901030624w4501e6f2l19d54a1e5223252c@mail.gmail.com>
On Sat, Jan 03, 2009 at 07:54:34PM +0530, Jaswinder Singh Rajput wrote:
> On Sat, Jan 3, 2009 at 7:15 PM, Willy Tarreau <w@1wt.eu> wrote:
> > On Sat, Jan 03, 2009 at 07:04:57PM +0530, Jaswinder Singh Rajput wrote:
> >> Hello Willy,
> >>
> >> Do you have any plans to add scripts/checkpatch.pl in 2.4 git.
> >
> > Not particularly planned, though I have nothing against including it if
> > some people want to use it.
> >
>
> Please add it. At least I can use it :-)
OK will do.
> >> Currently, what is the procedure to check patch for 2.4 git.
> >
> > Nowadays, 2.4 patches are so small that one's eyes are enough to check
> > for correctness ;-)
> >
>
> I ran 2.6 checkpatch.pl on some files and found lot of style problems
> like white spaces and indent.
> After fixing these problems code will be more read-able.
> I have plan to fix these problems on some important files. What you
> think about this.
I don't want to merge pure code cleanup patches, because :
1) it brings no added value to the final user
2) there's always a risk of regression
The only exception I accept to make is when I resync a file with 2.6 in
order to ease future patches.
However, I welcome cleanups which come with other changes/fixes, provided
they're not too invasive.
Regards,
Willy
prev parent reply other threads:[~2009-01-03 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 13:34 Jaswinder Singh Rajput
2009-01-03 13:45 ` Willy Tarreau
2009-01-03 14:24 ` Jaswinder Singh Rajput
2009-01-03 14:50 ` Willy Tarreau [this message]
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=20090103145024.GB21058@1wt.eu \
--to=w@1wt.eu \
--cc=apw@uk.ibm.com \
--cc=davej@redhat.com \
--cc=jaswinderlinux@gmail.com \
--cc=jschopp@austin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®