From: Samuel Ortiz <sameo@linux.intel.com>
To: Robert Dolca <robert.dolca@intel.com>
Cc: linux-nfc@lists.01.org,
Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Berg Johannes <johannes.berg@intel.com>,
Clement Perrochaud <clement.perrochaud@nxp.com>
Subject: Re: [PATCH v2 0/2] Add ACPI support for NXP PN544
Date: Wed, 28 Jan 2015 00:29:11 +0100 [thread overview]
Message-ID: <20150127232911.GC32667@ribalta.mp.intel.com> (raw)
In-Reply-To: <1422270817-10950-1-git-send-email-robert.dolca@intel.com>
Hi Robert,
On Mon, Jan 26, 2015 at 01:13:35PM +0200, Robert Dolca wrote:
> This patch set introduces ACPI support for PN544.
>
> gpio_set_value was replaced with gpio_set_value_cansleep in order
> to allow GPIO access that may sleep. This is particularelly useful
> when GPIO is accessed using busses like I2C, SPI, USB
>
> Changes since v1:
> - Added cover letter
> - Removed debug define and Kconfig include
> - Minor fixes to patch subjects
>
> Links to v1:
> - http://lkml.iu.edu/hypermail/linux/kernel/1501.1/00943.html
> - http://lkml.iu.edu/hypermail/linux/kernel/1501.1/00944.html
>
> Robert Dolca (2):
> NFC: PN544: GPIO access that may sleep
> NFC: Add ACPI support for NXP PN544
Both patches applied, many thanks.
Cheers,
Samuel.
prev parent reply other threads:[~2015-01-27 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 11:13 [PATCH v2 0/2] Add ACPI support for NXP PN544 Robert Dolca
2015-01-26 11:13 ` [PATCH v2 1/2] NFC: PN544: GPIO access that may sleep Robert Dolca
2015-01-26 11:13 ` [PATCH v2 2/2] NFC: Add ACPI support for NXP PN544 Robert Dolca
2015-01-27 23:28 ` Samuel Ortiz
2015-02-12 8:14 ` Uwe Kleine-König
2015-02-12 17:48 ` Robert Dolca
2015-02-12 19:26 ` Uwe Kleine-König
2015-01-27 23:29 ` Samuel Ortiz [this message]
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=20150127232911.GC32667@ribalta.mp.intel.com \
--to=sameo@linux.intel.com \
--cc=aloisio.almeida@openbossa.org \
--cc=clement.perrochaud@nxp.com \
--cc=davem@davemloft.net \
--cc=johannes.berg@intel.com \
--cc=lauro.venancio@openbossa.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfc@lists.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robert.dolca@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).