From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rehas Sachdeva <aquannie@gmail.com>
Cc: outreachy-kernel@googlegroups.com, linux-usb@vger.kernel.org,
Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
James Simmons <jsimmons@infradead.org>
Subject: Re: [PATCH 1/6] staging: lustre: Add space b/w concatenated strings
Date: Thu, 15 Sep 2016 12:19:08 +0200 [thread overview]
Message-ID: <20160915101908.GA22178@kroah.com> (raw)
In-Reply-To: <5f0049b66e2bf80634cf510e090e6b577302cedb.1473923837.git.aquannie@gmail.com>
On Thu, Sep 15, 2016 at 01:34:48PM +0530, Rehas Sachdeva wrote:
> Fixes checkpatch.pl warning:
> CHECK: Concatenated strings should use spaces between elements
>
> Signed-off-by: Rehas Sachdeva <aquannie@gmail.com>
> ---
> drivers/staging/lustre/lustre/fid/fid_request.c | 8 ++++----
> drivers/staging/lustre/lustre/fid/lproc_fid.c | 2 +-
> 2 files changed, 5 insertions(+), 5 deletions(-)
Why are you sending Lustre driver patches to the linux-usb mailing list?
totally confused,
greg k-h
next prev parent reply other threads:[~2016-09-15 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 8:04 [PATCH 0/6] staging: lustre: Fix multiple checkpatch warnings Rehas Sachdeva
2016-09-15 8:04 ` [PATCH 1/6] staging: lustre: Add space b/w concatenated strings Rehas Sachdeva
2016-09-15 10:19 ` Greg Kroah-Hartman [this message]
2016-09-15 11:58 ` Rehas Sachdeva
2016-09-15 8:05 ` [PATCH 2/6] staging: lustre: Fix block comment style Rehas Sachdeva
2016-09-15 8:06 ` [PATCH 4/6] staging: lustre: Change 'seq_printf' to 'seq_puts' Rehas Sachdeva
2016-09-15 8:07 ` [PATCH 5/6] staging: lustre: Remove unnecessary 'return' Rehas Sachdeva
2016-09-15 8:10 ` [Outreachy kernel] " Julia Lawall
2016-09-15 12:03 ` Rehas Sachdeva
2016-09-15 12:58 ` Rehas Sachdeva
2016-09-15 8:08 ` [PATCH 6/6] staging: lustre: Fix indentation Rehas Sachdeva
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=20160915101908.GA22178@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=aquannie@gmail.com \
--cc=jsimmons@infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=oleg.drokin@intel.com \
--cc=outreachy-kernel@googlegroups.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 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.