linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	linux-gpio@vger.kernel.org,
	David Cohen <david.a.cohen@linux.intel.com>
Subject: Re: [PATCH v1 2/2] gpio: intel-mid: Sort header block alphabetically
Date: Fri, 08 Jul 2016 12:11:30 +0300	[thread overview]
Message-ID: <1467969090.30123.504.camel@linux.intel.com> (raw)
In-Reply-To: <20160708082229.GX23527@lahna.fi.intel.com>

On Fri, 2016-07-08 at 11:22 +0300, Mika Westerberg wrote:
> On Wed, Jul 06, 2016 at 12:50:13PM +0300, Andy Shevchenko wrote:
> > Sort the header inclusion lines by alphabetical order.
> > 
> > While here, update Intel Copyright.
> > 
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> I don't see much point in patches like this but it does no harm so,

Consider this one is a part of a bundle. Otherwise I agree with you.

> 
> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>

Thanks!

-- 

Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2016-07-08  9:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  9:50 [PATCH v1 1/2] gpio: intel-mid: Remove potentially harmful code Andy Shevchenko
2016-07-06  9:50 ` [PATCH v1 2/2] gpio: intel-mid: Sort header block alphabetically Andy Shevchenko
2016-07-08  8:22   ` Mika Westerberg
2016-07-08  9:11     ` Andy Shevchenko [this message]
2016-07-11  8:56   ` Linus Walleij
2016-07-08  8:20 ` [PATCH v1 1/2] gpio: intel-mid: Remove potentially harmful code Mika Westerberg
2016-07-08  9:10   ` Andy Shevchenko
2016-07-11  8:54 ` Linus Walleij

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=1467969090.30123.504.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=david.a.cohen@linux.intel.com \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@linux.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).