public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Michael Shuey <shuey@purdue.edu>
Cc: "oleg.drokin@intel.com" <oleg.drokin@intel.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"HPDD-discuss@ml01.01.org" <HPDD-discuss@ml01.01.org>
Subject: Re: [PATCH] staging: lustre: code cleanup - variable declaration spacing
Date: Wed, 6 May 2015 18:05:42 +0300	[thread overview]
Message-ID: <20150506150542.GR16501@mwanda> (raw)
In-Reply-To: <CABqvwjsia7nqfZtAP4T_DSKRTjdaNZa=7RxXJuZeVxHK7Y2z_Q@mail.gmail.com>

On Wed, May 06, 2015 at 10:47:56AM -0400, Michael Shuey wrote:
> Sudip, Dan, thanks for your feedback.  I'll see what I can do to clean up
> the trimmings in my next iteration (and add more files' worth of cleanup as
> well).
> 
> While editing these 4 files, I found two more (non-white space) clean ups
> needed.  Should I build a patch series, with those fixes in it, or email
> those as a separate patch?

They probably have to be applied in order so it needs to be a patch
series.

regards,
dan carpenter


  parent reply	other threads:[~2015-05-06 15:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 12:02 [PATCH] staging: lustre: code cleanup - variable declaration spacing Mike Shuey
2015-05-06 12:36 ` Sudip Mukherjee
2015-05-06 13:52 ` Dan Carpenter
     [not found]   ` <CABqvwjsia7nqfZtAP4T_DSKRTjdaNZa=7RxXJuZeVxHK7Y2z_Q@mail.gmail.com>
2015-05-06 15:05     ` Dan Carpenter [this message]
2015-05-07  3:36 ` [HPDD-discuss] " Dilger, Andreas
2015-05-07 12:09   ` Dan Carpenter
2015-05-07 15:32     ` Julia Lawall
2015-05-08  1:32     ` Drokin, Oleg

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=20150506150542.GR16501@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=HPDD-discuss@ml01.01.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg.drokin@intel.com \
    --cc=shuey@purdue.edu \
    /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