From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>,
lustre-devel@lists.lustre.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] Staging: Luster: Clean up line over 80Char in lib-lnet.h
Date: Tue, 11 Jul 2017 19:13:40 +0200 [thread overview]
Message-ID: <20170711171340.GB11838@kroah.com> (raw)
In-Reply-To: <64eeec691ca65e0fa68f2fcc5e7a04518f4971b8.1499388016.git.Craig@craiginches.com>
On Fri, Jul 07, 2017 at 01:46:42AM +0000, Craig Inches wrote:
> This patch fixes a warning generated by checkpatch for
> a line over 80 characters.
>
> Signed-off-by: Craig Inches <Craig@craiginches.com>
> ---
> drivers/staging/lustre/include/linux/lnet/lib-lnet.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Your subject line mispelled the filesystem's name :(
next prev parent reply other threads:[~2017-07-11 17:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 1:46 [PATCH 0/4] Staging: Lustre Style Fixes Craig Inches
2017-07-07 1:46 ` [PATCH 1/4] Staging: Luster: Clean up line over 80Char in lib-lnet.h Craig Inches
2017-07-11 17:13 ` Greg Kroah-Hartman [this message]
2017-07-07 1:46 ` [PATCH 2/4] Staging: Lustre Fix up multiple Block Comments in lib-types.h Craig Inches
2017-07-07 1:47 ` [PATCH 3/4] Staging: Lustre Fixing multiline block comments in lnetst.h Craig Inches
2017-07-11 17:14 ` Greg Kroah-Hartman
2017-07-12 5:09 ` Dilger, Andreas
2017-07-07 1:47 ` [PATCH 4/4] Staging: Lustre Fix block statement style issue Craig Inches
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=20170711171340.GB11838@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.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