From: Michael Shuey <shuey@purdue.edu>
To: "Simmons, James A." <simmonsja@ornl.gov>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
James Simmons <jsimmons@infradead.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Oleg Drokin <oleg.drokin@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] [PATCH 1/3] staging: lustre: checkpatch cleanups for nidstring.c
Date: Sun, 1 Nov 2015 18:24:18 -0500 [thread overview]
Message-ID: <CABqvwjtkS-uQH5e0zbCKFq3pkZSGrj6wo80SDa6PLgtKFVgUTA@mail.gmail.com> (raw)
In-Reply-To: <229dae23c2f34950a21db4bd6dbdcfba@EXCHCS32.ornl.gov>
I suspect you're over-thinking it. The maintainers appear to be
reacting to the different types of style changes - "checkpatch
cleanups" is an awfully broad commit message. I'd suggest breaking
this patch (and any others like it) into two pieces; one with
whitespace cleanups, and one with the "== NULL" fixes (and mentioning
both by kind in the commit message, rather than just attributing to
checkpatch). Then issue a v2 of the series, and see where you land.
Of course, YMMV. :-)
--
Mike Shuey
On Sun, Nov 1, 2015 at 6:07 PM, Simmons, James A. <simmonsja@ornl.gov> wrote:
>>On Thu, Oct 29, 2015 at 07:28:21PM -0400, James Simmons wrote:
>>> With nidstring now having the latest fixes we can
>>> now clean up all the remaining checkpatch errors
>>> for nidstring.c.
>>
>>Please be specific as to exactly what you changed, and break it up into
>>one-patch-per-thing. And no, "fix all checkpatch errors" is not "one
>>thing"
>
> Hmm. This makes me think I might be going about this wrong. Instead of
> doing style changes per file I should be doing one style change per subsystem
> instead. Unless you prefer doing these style changes on per file base. Perhaps
> for now I should focus on pushing the fixes that have cumulated and once
> caught up then finished off the style issues.
> _______________________________________________
> lustre-devel mailing list
> lustre-devel@lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
next prev parent reply other threads:[~2015-11-01 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 23:28 [PATCH 0/3] make nidstring.c kernel style compliant James Simmons
2015-10-29 23:28 ` [PATCH 1/3] staging: lustre: checkpatch cleanups for nidstring.c James Simmons
2015-10-30 7:50 ` Sudip Mukherjee
2015-10-30 23:01 ` Greg Kroah-Hartman
2015-11-01 23:07 ` [lustre-devel] " Simmons, James A.
2015-11-01 23:24 ` Michael Shuey [this message]
2015-11-02 14:48 ` Dan Carpenter
2015-11-03 23:56 ` Simmons, James A.
2015-10-29 23:28 ` [PATCH 2/3] staging: lustre: white space " James Simmons
2015-10-29 23:28 ` [PATCH 3/3] staging: lustre: checkpatch cleanups for nidstr.h James Simmons
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=CABqvwjtkS-uQH5e0zbCKFq3pkZSGrj6wo80SDa6PLgtKFVgUTA@mail.gmail.com \
--to=shuey@purdue.edu \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--cc=simmonsja@ornl.gov \
/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).