From: Michal Simek <michal.simek@xilinx.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
<linux-kernel@vger.kernel.org>
Cc: <linux-renesas-soc@vger.kernel.org>,
<kernel-janitors@vger.kernel.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Joshua Kinard <kumba@gentoo.org>,
Vladimir Zapolskiy <vz@mleia.com>,
Sylvain Lemieux <slemieux.tyco@gmail.com>,
Michal Simek <michal.simek@xilinx.com>,
<linux-rtc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 44/61] rtc: simplify getting .drvdata
Date: Fri, 20 Apr 2018 09:24:26 +0200 [thread overview]
Message-ID: <6c43fc08-4f73-601f-228c-9a4202d5b5c5@xilinx.com> (raw)
In-Reply-To: <20180419140641.27926-45-wsa+renesas@sang-engineering.com>
On 19.4.2018 16:06, Wolfram Sang wrote:
> We should get drvdata from struct device directly. Going via
> platform_device is an unneeded step back and forth.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> Build tested only. buildbot is happy. Please apply individually.
>
> drivers/rtc/rtc-bq4802.c | 6 ++----
> drivers/rtc/rtc-ds1216.c | 6 ++----
> drivers/rtc/rtc-ds1511.c | 9 +++------
> drivers/rtc/rtc-ds1553.c | 15 +++++----------
> drivers/rtc/rtc-ds1685.c | 21 +++++++--------------
> drivers/rtc/rtc-ds1742.c | 6 ++----
> drivers/rtc/rtc-lpc32xx.c | 16 ++++++----------
> drivers/rtc/rtc-m48t59.c | 41 ++++++++++++++++-------------------------
> drivers/rtc/rtc-mv.c | 3 +--
> drivers/rtc/rtc-mxc.c | 21 +++++++--------------
> drivers/rtc/rtc-pcap.c | 15 +++++----------
> drivers/rtc/rtc-sh.c | 15 +++++----------
> drivers/rtc/rtc-stk17ta8.c | 15 +++++----------
> drivers/rtc/rtc-test.c | 3 +--
> drivers/rtc/rtc-zynqmp.c | 10 ++++------
Acked-by: Michal Simek <michal.simek@xilinx.com> (for zynqmp)
Thanks,
Michal
next prev parent reply other threads:[~2018-04-20 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 14:05 [PATCH 00/61] tree-wide: simplify getting .drvdata Wolfram Sang
2018-04-19 14:06 ` [PATCH 44/61] rtc: " Wolfram Sang
2018-04-20 7:24 ` Michal Simek [this message]
2018-05-03 20:09 ` Alexandre Belloni
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=6c43fc08-4f73-601f-228c-9a4202d5b5c5@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kumba@gentoo.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=slemieux.tyco@gmail.com \
--cc=vz@mleia.com \
--cc=wsa+renesas@sang-engineering.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).