public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
	devel@driverdev.osuosl.org, max@stro.at, jbrenner@taosinc.com,
	grundler@chromium.org, linux-kernel@vger.kernel.org,
	bfreed@chromium.org, linux-iio@vger.kernel.org, jic23@cam.ac.uk
Subject: Re: [PATCH V4 1/2] staging: iio: light: convert multiple spaces to tab
Date: Fri, 20 Apr 2012 08:52:53 -0700	[thread overview]
Message-ID: <20120420155253.GC8327@kroah.com> (raw)
In-Reply-To: <4F9146D8.4060608@metafoo.de>

On Fri, Apr 20, 2012 at 01:22:00PM +0200, Lars-Peter Clausen wrote:
> On 04/20/2012 09:27 AM, Laxman Dewangan wrote:
> > Using tab inplace of multiple spaces for indenting.
> > 
> > Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> > ---
> > Changes from V1:
> > As per Jonathan's feedback, creating this patch for only
> > indenting cleanups.
> > No change from V2
> > No Change from V3
> > 
> > This is already acked by Jonathan.
> 
> When resending a patch that has already been acked or reviewed, include the
> Acked-by or Reviewed-by line in the patch under your Signed-off-by.

I've now applied this patch, so it no longer needs to be resent.

thanks,

greg k-h

  reply	other threads:[~2012-04-20 15:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20  7:27 [PATCH V4 0/2] staging: iio: light: use regmap in isl29018 for register access Laxman Dewangan
2012-04-20  7:27 ` [PATCH V4 1/2] staging: iio: light: convert multiple spaces to tab Laxman Dewangan
2012-04-20 11:22   ` Lars-Peter Clausen
2012-04-20 15:52     ` Greg KH [this message]
2012-04-20  7:27 ` [PATCH V4 2/2] staging: iio: light: isl29018: use regmap for register access Laxman Dewangan
2012-04-20 15:04   ` Grant Grundler

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=20120420155253.GC8327@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bfreed@chromium.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=grundler@chromium.org \
    --cc=jbrenner@taosinc.com \
    --cc=jic23@cam.ac.uk \
    --cc=lars@metafoo.de \
    --cc=ldewangan@nvidia.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@stro.at \
    /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