From: Joe Perches <joe@perches.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH v3 6/7] staging:lustre: style cleanups for lib-socket.c
Date: Wed, 03 Jun 2015 10:16:44 -0700 [thread overview]
Message-ID: <1433351804.4861.134.camel@perches.com> (raw)
In-Reply-To: <b8dcda1e71e843699993f689521336bf@EXCHCS32.ornl.gov>
On Wed, 2015-06-03 at 17:12 +0000, Simmons, James A. wrote:
> >On Wed, 2015-06-03 at 10:32 -0400, James Simmons wrote:
> >> Handle all the style issues reported by checkpatch.pl.
> >> Remove general white spaces, spaces in function calls,
> >> etc.
> >[]
> >> @@ -167,13 +164,14 @@ lnet_ipif_enumerate (char ***namesp)
> >> if (nalloc * sizeof(*ifr) > PAGE_CACHE_SIZE) {
> >> toobig = 1;
> >> nalloc = PAGE_CACHE_SIZE/sizeof(*ifr);
> >> - CWARN("Too many interfaces: only enumerating first %d\n",
> >> - nalloc);
> >> + CWARN("Too many interfaces: only enumerating "
> >> + "first %d\n", nalloc);
> >
> >Please don't split single strings into multiple parts.
> >
> >For a patch like this it'd be nice to specify that both
> >"git diff -w" and scripts/objdiff shows no differences.
> >
> >Unless it does...
>
> Two patches have mistakes. Should I send a new series or do a in-reply instead.
Most of the time, it's better to send a new series.
If any of the unmodified patches are very large, like 100KB+,
then it can be better to send individually updated patches.
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: "Simmons, James A." <simmonsja@ornl.gov>
Cc: James Simmons <jsimmons@infradead.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"HPDD-discuss@lists.01.org" <HPDD-discuss@ml01.01.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Oleg Drokin <oleg.drokin@intel.com>,
"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] [PATCH v3 6/7] staging:lustre: style cleanups for lib-socket.c
Date: Wed, 03 Jun 2015 10:16:44 -0700 [thread overview]
Message-ID: <1433351804.4861.134.camel@perches.com> (raw)
In-Reply-To: <b8dcda1e71e843699993f689521336bf@EXCHCS32.ornl.gov>
On Wed, 2015-06-03 at 17:12 +0000, Simmons, James A. wrote:
> >On Wed, 2015-06-03 at 10:32 -0400, James Simmons wrote:
> >> Handle all the style issues reported by checkpatch.pl.
> >> Remove general white spaces, spaces in function calls,
> >> etc.
> >[]
> >> @@ -167,13 +164,14 @@ lnet_ipif_enumerate (char ***namesp)
> >> if (nalloc * sizeof(*ifr) > PAGE_CACHE_SIZE) {
> >> toobig = 1;
> >> nalloc = PAGE_CACHE_SIZE/sizeof(*ifr);
> >> - CWARN("Too many interfaces: only enumerating first %d\n",
> >> - nalloc);
> >> + CWARN("Too many interfaces: only enumerating "
> >> + "first %d\n", nalloc);
> >
> >Please don't split single strings into multiple parts.
> >
> >For a patch like this it'd be nice to specify that both
> >"git diff -w" and scripts/objdiff shows no differences.
> >
> >Unless it does...
>
> Two patches have mistakes. Should I send a new series or do a in-reply instead.
Most of the time, it's better to send a new series.
If any of the unmodified patches are very large, like 100KB+,
then it can be better to send individually updated patches.
next prev parent reply other threads:[~2015-06-03 17:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 14:32 [lustre-devel] [PATCH v3 0/7] staging:lustre: remove tcpip abstraction from libcfs James Simmons
2015-06-03 14:32 ` James Simmons
2015-06-03 14:32 ` [lustre-devel] [PATCH v3 1/7] staging:lustre: move tcpip abstraction James Simmons
2015-06-03 14:32 ` James Simmons
2015-06-03 14:32 ` [lustre-devel] [PATCH v3 2/7] staging:lustre: remove useless libcfs_sock_release James Simmons
2015-06-03 14:32 ` James Simmons
2015-06-03 14:32 ` [lustre-devel] [PATCH v3 3/7] staging:lustre: remove useless libcfs_sock_abort_accept James Simmons
2015-06-03 14:32 ` James Simmons
2015-06-03 14:32 ` [lustre-devel] [PATCH v3 4/7] staging:lustre: rename tcpip handling functions to lnet_* prefix James Simmons
2015-06-03 14:32 ` James Simmons
2015-06-03 16:33 ` [lustre-devel] " Sudip Mukherjee
2015-06-03 16:33 ` Sudip Mukherjee
2015-06-03 16:38 ` [lustre-devel] " Simmons, James A.
2015-06-03 16:38 ` Simmons, James A.
2015-06-03 16:42 ` Sudip Mukherjee
2015-06-03 16:42 ` Sudip Mukherjee
2015-06-03 14:32 ` [lustre-devel] [PATCH v3 5/7] staging:lustre: use available kernel wrappers in lib-socket.c James Simmons
2015-06-03 14:32 ` James Simmons
2015-06-03 14:32 ` [lustre-devel] [PATCH v3 6/7] staging:lustre: style cleanups for lib-socket.c James Simmons
2015-06-03 14:32 ` James Simmons
2015-06-03 14:42 ` [lustre-devel] " Joe Perches
2015-06-03 14:42 ` Joe Perches
2015-06-03 17:12 ` [lustre-devel] " Simmons, James A.
2015-06-03 17:12 ` Simmons, James A.
2015-06-03 17:16 ` Joe Perches [this message]
2015-06-03 17:16 ` Joe Perches
2015-06-03 14:32 ` [lustre-devel] [PATCH v3 7/7] staging:lustre: Update license and copyright " James Simmons
2015-06-03 14:32 ` 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=1433351804.4861.134.camel@perches.com \
--to=joe@perches.com \
--cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.