From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Simmons, James A." <simmonsja@ornl.gov>
Cc: "'Sudip Mukherjee'" <sudipm.mukherjee@gmail.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Oleg Drokin <oleg.drokin@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] [PATCH v2 1/7] staging: lustre: remove white space in libcfs_hash.h
Date: Wed, 4 Nov 2015 09:20:19 -0800 [thread overview]
Message-ID: <20151104172019.GB8504@kroah.com> (raw)
In-Reply-To: <12a3bc6fd3414ba5b4fac029749675db@EXCHCS32.ornl.gov>
On Wed, Nov 04, 2015 at 03:07:13PM +0000, Simmons, James A. wrote:
> >On Tue, Nov 03, 2015 at 07:46:07PM -0800, Greg Kroah-Hartman wrote:
> >> On Mon, Nov 02, 2015 at 12:22:07PM -0500, James Simmons wrote:
> >> > Cleanup all the unneeded white space in libcfs_hash.h.
> >> >
> >> > Signed-off-by: James Simmons <jsimmons@infradead.org>
> >> > ---
> >> > .../lustre/include/linux/libcfs/libcfs_hash.h | 135 ++++++++++----------
> >> > 1 files changed, 70 insertions(+), 65 deletions(-)
> >>
> >> Doesn't apply, did I already queue up this series?
> >
> >No. This did not apply because of:
> >c7fdf4a3959f ("staging: lustre: fix remaining checkpatch issues for libcfs_hash.h")
>
> Surprise this was merged which is why I did a second series for this.
Oops, my mistake, I've now dropped this patch from my tree. Please
resend this series so I can try to sync up properly.
thanks,
greg k-h
next prev parent reply other threads:[~2015-11-04 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 17:22 [PATCH v2 0/7] staging: lustre: second series for libcfs hash code cleanup James Simmons
2015-11-02 17:22 ` [PATCH v2 1/7] staging: lustre: remove white space in libcfs_hash.h James Simmons
2015-11-04 3:46 ` Greg Kroah-Hartman
2015-11-04 11:41 ` Sudip Mukherjee
2015-11-04 15:07 ` [lustre-devel] " Simmons, James A.
2015-11-04 17:20 ` Greg Kroah-Hartman [this message]
2015-11-04 15:05 ` Simmons, James A.
2015-11-02 17:22 ` [PATCH v2 2/7] staging: lustre: remove obsolete comment " James Simmons
2015-11-02 17:22 ` [PATCH v2 3/7] staging: lustre: move linux hash.h header to start of libcfs_hash.h James Simmons
2015-11-02 17:22 ` [PATCH v2 4/7] staging: lustre: use proper comment blocks for libcfs_hash.h James Simmons
2015-11-02 17:22 ` [PATCH v2 5/7] staging: lustre: handle NULL comparisons correctly " James Simmons
2015-11-02 17:22 ` [PATCH v2 6/7] staging: lustre: remove white space in hash.c James Simmons
2015-11-02 17:22 ` [PATCH v2 7/7] staging: lustre: place linux header first " 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=20151104172019.GB8504@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=oleg.drokin@intel.com \
--cc=simmonsja@ornl.gov \
--cc=sudipm.mukherjee@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;
as well as URLs for NNTP newsgroup(s).