All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Cohen <david.a.cohen@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] gpio-langwell: bugfix and amendments
Date: Tue, 21 May 2013 10:23:37 -0700	[thread overview]
Message-ID: <519BAD99.9020007@intel.com> (raw)
In-Reply-To: <1369132386-11725-1-git-send-email-andriy.shevchenko@linux.intel.com>

Hi Andy,

Thanks for the patches. :)

On 05/21/2013 03:33 AM, Andy Shevchenko wrote:
> There is locking bug fix and few amendments. Each commit message verbose
> enoough I think.
>
> Andy Shevchenko (4):
>    gpio-langwell: initialize lock before usage
>    gpio-langwell: amend error messages
>    gpio-langwell: do not use direct access to iomapped memory
>    gpio-langwell: use managed functions pcim_* and devm_*

I wonder if you should rebase those patches on top of this one:
https://patchwork.kernel.org/patch/2527431/

Maybe Linux Walleij knows better.

Br, David Cohen

>   drivers/gpio/gpio-langwell.c | 93 +++++++++++++-------------------------------
>   1 file changed, 28 insertions(+), 65 deletions(-)
>


  parent reply	other threads:[~2013-05-21 17:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21 10:33 [PATCH 0/4] gpio-langwell: bugfix and amendments Andy Shevchenko
2013-05-21 10:33 ` [PATCH 1/4] gpio-langwell: initialize lock before usage Andy Shevchenko
2013-05-21 10:33 ` [PATCH 2/4] gpio-langwell: amend error messages Andy Shevchenko
2013-05-21 10:33 ` [PATCH 3/4] gpio-langwell: do not use direct access to iomapped memory Andy Shevchenko
2013-05-21 10:33 ` [PATCH 4/4] gpio-langwell: use managed functions pcim_* and devm_* Andy Shevchenko
2013-05-21 17:23 ` David Cohen [this message]
2013-05-21 17:49   ` [PATCH 0/4] gpio-langwell: bugfix and amendments Andy Shevchenko

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=519BAD99.9020007@intel.com \
    --to=david.a.cohen@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.