From: Craig Inches <craig@craiginches.com>
To: "Dilger, Andreas" <andreas.dilger@intel.com>
Cc: "Drokin, Oleg" <oleg.drokin@intel.com>,
James Simmons <jsimmons@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 4/4] Staging: Lustre Fix block statement style issue
Date: Mon, 17 Jul 2017 17:50:27 +0000 (UTC) [thread overview]
Message-ID: <20170717175017.GA32268@battlestar> (raw)
In-Reply-To: <F6F7D587-CD46-40B8-A5B5-678B6A16AD8F@intel.com>
On Mon, Jul 17, 2017 at 05:44:59PM +0000, Dilger, Andreas wrote:
> On Jul 12, 2017, at 03:03, Craig Inches <craig@craiginches.com> wrote:
> >
> > This fixes a block statement which didnt end with */
> >
> > Signed-off-by: Craig Inches <Craig@craiginches.com>
> > ---
> > drivers/staging/lustre/include/linux/lnet/socklnd.h | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/staging/lustre/include/linux/lnet/socklnd.h b/drivers/staging/lustre/include/linux/lnet/socklnd.h
> > index dd5bc0e46560..a1ae66ede7a8 100644
> > --- a/drivers/staging/lustre/include/linux/lnet/socklnd.h
> > +++ b/drivers/staging/lustre/include/linux/lnet/socklnd.h
> > @@ -76,7 +76,8 @@ struct ksock_msg {
> > __u64 ksm_zc_cookies[2]; /* Zero-Copy request/ACK cookie */
> > union {
> > struct ksock_lnet_msg lnetmsg; /* lnet message, it's empty if
> > - * it's NOOP */
> > + * it's NOOP
> > + */
>
> Rather than making the multi-line comments even more space consuming (I'm not a big
> fan of "*/ must be on a line by itself" since it wastes a lot of vertical space),
> I'd prefer to just shorten the comment, if possible, like:
>
> struct ksock_lnet_msg lnetmsg; /* lnet message, empty if NOOP */
That makes sense, I believe the series has already made it to
staging-next, so not sure what the process would be to fix it up.
I am doing another set of style fixes which I can include this change
aswell.
Cheers,
Craig
next prev parent reply other threads:[~2017-07-17 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 9:02 [PATCH v2 0/4] Staging: Lustre Style Fixes Craig Inches
2017-07-12 9:02 ` [PATCH v2 1/4] Staging: Lustre Clean up line over 80Char in lib-lnet.h Craig Inches
2017-07-12 9:02 ` [PATCH v2 2/4] Staging: Lustre Fix up multiple Block Comments in lib-types.h Craig Inches
2017-07-12 9:03 ` [PATCH v2 3/4] Staging: Lustre Fixing multiline block comments in lnetst.h Craig Inches
2017-07-12 9:03 ` [PATCH v2 4/4] Staging: Lustre Fix block statement style issue Craig Inches
2017-07-17 17:44 ` Dilger, Andreas
2017-07-17 17:50 ` Craig Inches [this message]
2017-07-17 18:21 ` Dan Carpenter
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=20170717175017.GA32268@battlestar \
--to=craig@craiginches.com \
--cc=andreas.dilger@intel.com \
--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 \
/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
Powered by JetHome