From: Samuel Ortiz <sameo@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-wireless@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v3 1/5] NFC: pn544: Get rid of platform data
Date: Wed, 5 Apr 2017 10:06:18 +0200 [thread overview]
Message-ID: <20170405080618.GA2136@zurbaran.ger.intel.com> (raw)
In-Reply-To: <20170328093639.53481-1-andriy.shevchenko@linux.intel.com>
Hi Andy,
On Tue, Mar 28, 2017 at 12:36:35PM +0300, Andy Shevchenko wrote:
> Legacy platform data must go away. We are on the safe side here since
> there are no users of it in the kernel.
>
> If anyone by any odd reason needs it the GPIO lookup tables and
> built-in device properties at your service.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> v3: no change
>
> drivers/nfc/pn544/i2c.c | 43 ++++++-------------------------------
> include/linux/platform_data/pn544.h | 43 -------------------------------------
> 2 files changed, 6 insertions(+), 80 deletions(-)
> delete mode 100644 include/linux/platform_data/pn544.h
All 5 patches applied to nfc-next.
Cheers,
Samuel.
prev parent reply other threads:[~2017-04-05 8:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 9:36 [PATCH v3 1/5] NFC: pn544: Get rid of platform data Andy Shevchenko
2017-03-28 9:36 ` [PATCH v3 2/5] NFC: pn544: Covert to use GPIO descriptor Andy Shevchenko
2017-03-28 9:36 ` [PATCH v3 3/5] NFC: pn544: Convert to use devm_request_threaded_irq() Andy Shevchenko
2017-03-28 9:36 ` [PATCH v3 4/5] NFC: pn544: Add GPIO ACPI mapping table Andy Shevchenko
2017-03-28 9:36 ` [PATCH v3 5/5] NFC: pn544: Get rid of code duplication in ->probe() Andy Shevchenko
2017-04-04 16:15 ` [PATCH v3 1/5] NFC: pn544: Get rid of platform data Andy Shevchenko
2017-04-05 8:06 ` 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=20170405080618.GA2136@zurbaran.ger.intel.com \
--to=sameo@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-wireless@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).