From: Greg KH <gregkh@linuxfoundation.org>
To: Sabin Mihai Rapan <sabin.rapan@gmail.com>
Cc: jsimmons@infradead.org, andreas.dilger@intel.com,
leg.drokin@intel.com, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: lustre: Fix trivial checkpatch warnings
Date: Mon, 14 May 2018 11:54:50 +0000 [thread overview]
Message-ID: <20180514115450.GA18400@kroah.com> (raw)
In-Reply-To: <20180512110216.6851-1-sabin.rapan@gmail.com>
On Sat, May 12, 2018 at 01:02:16PM +0200, Sabin Mihai Rapan wrote:
> Trivial fix to multiple errors and warnings in the lustre headers.
Please be specific as to what you are fixing. This should be broken up
into "one patch per logical change". Please fix up and resend the whole
series.
thanks,
greg k-h
prev parent reply other threads:[~2018-05-14 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 11:02 [PATCH 2/2] staging: lustre: Fix trivial checkpatch warnings Sabin Mihai Rapan
2018-05-14 11:54 ` Greg KH [this message]
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=20180514115450.GA18400@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=jsimmons@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=leg.drokin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sabin.rapan@gmail.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