From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] rtc: m41t80: Simplify probe()
Date: Mon, 28 Aug 2023 14:29:57 +0300 [thread overview]
Message-ID: <ZOyFNeMOxMenMdl0@smile.fi.intel.com> (raw)
In-Reply-To: <OS0PR01MB592250E1368B54DEC421837A86E0A@OS0PR01MB5922.jpnprd01.prod.outlook.com>
On Mon, Aug 28, 2023 at 11:13:29AM +0000, Biju Das wrote:
> > On Mon, Aug 28, 2023 at 10:27:37AM +0100, Biju Das wrote:
...
> > > + m41t80_data->features = (unsigned long)i2c_get_match_data(client);
> >
> > uintptr_t is more natural and de facto pattern for this. Why unsigned long
> > is here?
>
> I just used the casting used for of_device_get_match_data.
> I will change it to uintptr_t, If there is no objection.
>
> - m41t80_data->features = (unsigned long)
> - of_device_get_match_data(&client->dev);
Yes, but for new APIs the uintptr_t is natural (de facto).
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-08-28 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 9:27 [PATCH] rtc: m41t80: Simplify probe() Biju Das
2023-08-28 11:10 ` Andy Shevchenko
2023-08-28 11:13 ` Biju Das
2023-08-28 11:29 ` Andy Shevchenko [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=ZOyFNeMOxMenMdl0@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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 read-only IMAP folder(s) and NNTP newsgroup(s).