On Tue, Nov 20, 2018 at 11:27:57PM +0100, Alexandre Belloni wrote:
> Hello,
>
> (Please update my email address).
I will follow all recommendations.
New version coming soon...
Thanks for review!
>
> On 13/11/2018 19:17:10+0200, Andy Shevchenko wrote:
> > There are users which print time and da
Hello,
(Please update my email address).
On 13/11/2018 19:17:10+0200, Andy Shevchenko wrote:
> There are users which print time and date represented by content of
> struct rtc_time in human readable format.
>
> Instead of open coding that each time introduce %ptR[dt][rv] specifier.
>
> Note, us
On Tue, Nov 13, 2018 at 7:37 PM Joe Perches wrote:
>
> On Tue, 2018-11-13 at 19:17 +0200, Andy Shevchenko wrote:
> > There are users which print time and date represented by content of
> > struct rtc_time in human readable format.
> >
> > Instead of open coding that each time introduce %ptR[dt][rv
On Tue, 2018-11-13 at 19:17 +0200, Andy Shevchenko wrote:
> There are users which print time and date represented by content of
> struct rtc_time in human readable format.
>
> Instead of open coding that each time introduce %ptR[dt][rv] specifier.
>
> Note, users have to select PRINTK_PEXT_TIMEDA
There are users which print time and date represented by content of
struct rtc_time in human readable format.
Instead of open coding that each time introduce %ptR[dt][rv] specifier.
Note, users have to select PRINTK_PEXT_TIMEDATE option in a Kconfig.
Cc: Arnd Bergmann
Cc: Bartlomiej Zolnierkiew
5 matches
Mail list logo
