[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170827192638.2wgkhr7k3n4vrqth@piout.net>
Date: Sun, 27 Aug 2017 21:26:38 +0200
From: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Andreas Färber <afaerber@...e.de>,
linux-rtc@...r.kernel.org, Alessandro Zummo <a.zummo@...ertech.it>,
Roc He <hepeng@...oo.tv>,
????????? <jiang.liqin@...iatech.com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 2/3] rtc: Add Realtek RTD1295
On 27/08/2017 at 15:37:51 +0200, Andrew Lunn wrote:
> > >> +static inline int rtd119x_rtc_year_days(int year)
> > >> +{
> > >> + return rtc_year_days(1, 12, year);
> > >
> > > I'm not sure it is worth wrapping rtc_year_days
> > [snip]
> >
> > Well, I found your rtc_year_days rather confusing and had to play with
> > the arguments until I got it working as expected, so I wanted an inline
> > function (or macro) as abstraction from my three callers.
>
> I agree with that. I was wondering why 1st December was being used. I
> would say this API does not do too well on Rusty's API Design
> Manifesto.
>
It follows the convention that tm_mon is 0-11. Making it easy to read
for anyone used to the RTC subsystem. I can agree it is not the most
intuitive one. That choice predates the RTC subsystem (made in 1996), I
won't give any name ;)
> It does at least get the day/month/year in the right order ;-)
>
> Andrew
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
Powered by blists - more mailing lists