linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Simmons, James A." <simmonsja@ornl.gov>
To: "'Greg Kroah-Hartman'" <gregkh@linuxfoundation.org>,
	James Simmons <jsimmons@infradead.org>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: RE: [PATCH v2 1/7] staging: lustre: remove white space in libcfs_hash.h
Date: Wed, 4 Nov 2015 15:05:41 +0000	[thread overview]
Message-ID: <e1ec3a1b2a6d435ba72d880e301cf3d1@EXCHCS32.ornl.gov> (raw)
In-Reply-To: <20151104034607.GA12870@kroah.com>

>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?

I did a second version of those patches. In one batch you will notice [PATCH v2].
The reason I did a second batch was to break up the "fix checkpatch issues" patch
in the first series. I was trying to behave :-)

  parent reply	other threads:[~2015-11-04 15:05 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
2015-11-04 15:05     ` Simmons, James A. [this message]
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=e1ec3a1b2a6d435ba72d880e301cf3d1@EXCHCS32.ornl.gov \
    --to=simmonsja@ornl.gov \
    --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;
as well as URLs for NNTP newsgroup(s).