From: RAGHU H <raghuhack78@gmail.com>
To: Joe Perches <joe@perches.com>,
m=@raghu-VirtualBox, Bart.VanAssche@wdc.com
Cc: Bart Van Assche <Bart.VanAssche@wdc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [PATCH] pktcdvd:checkpatch:fix pointer declaration
Date: Wed, 18 Jul 2018 23:25:53 +0530 [thread overview]
Message-ID: <20180718175553.GA5532@raghu-VirtualBox> (raw)
In-Reply-To: <47fc6920ec365a11b06f7c44f4a3f8d73d177e67.camel@perches.com>
Bart,
I'm starter in kernel contribution & I guess cleanup of certain files
which have more than 50+ checkpatch errors is good start.
Also one of the patch was accepted by Jens Axboe & he responded back to
resend one of the patch which was not getting applied.
But I get your point ,I'll restrict my checkpatch fixes to drivers/staging files
Thanks Joe for followup.
On Wed, Jul 18, 2018 at 11:43:11AM -0700, Joe Perches wrote:
> On Wed, 2018-07-18 at 18:06 +0000, Bart Van Assche wrote:
> > On Wed, 2018-07-18 at 21:28 +0530, RAGHU Halharvi wrote:
> > > * Fix all pointer declaration which causes
> > > "ERROR: "foo* bar" should be "foo *bar""
> >
> > Hello Raghu,
> >
> > If you would not be aware of this, checkpatch is a tool that is intended to
> > verify patches before submission and not to verify code that is already
> > upstream. A detailed explanation of why patches like this one should not be
> > submitted is available in "A quick guide to why stand-alone checkpatch
> > patches suck"
> > (https://lists.kernelnewbies.org/pipermail/kernelnewbies/2014-September/012296.html).
>
> Read more of the whole thread.
> Varying opinions exist.
>
next prev parent reply other threads:[~2018-07-18 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 15:58 [PATCH] pktcdvd:checkpatch:fix pointer declaration RAGHU Halharvi
2018-07-18 18:06 ` Bart Van Assche
2018-07-18 18:43 ` Joe Perches
2018-07-18 17:55 ` RAGHU H [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-18 14:59 RAGHU Halharvi
2018-07-17 18:01 RAGHU Halharvi
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=20180718175553.GA5532@raghu-VirtualBox \
--to=raghuhack78@gmail.com \
--cc=Bart.VanAssche@wdc.com \
--cc=axboe@kernel.dk \
--cc=joe@perches.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m=@raghu-VirtualBox \
/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).