Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934548AbdGTKds (ORCPT ); Thu, 20 Jul 2017 06:33:48 -0400 Received: from mga04.intel.com ([192.55.52.120]:36138 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934145AbdGTKdq (ORCPT ); Thu, 20 Jul 2017 06:33:46 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,383,1496127600"; d="scan'208";a="113459064" Message-ID: <1500546822.29303.136.camel@linux.intel.com> Subject: Re: [PATCH v1 00/25] lib, rtc: Print rtc_time via %pt[dt][rv] From: Andy Shevchenko To: Mark Salyzyn , Joe Perches , Rasmus Villemoes , Greg Kroah-Hartman , Andrew Morton , linux-kernel@vger.kernel.org, Alessandro Zummo , Alexandre Belloni , linux-rtc@vger.kernel.org Date: Thu, 20 Jul 2017 13:33:42 +0300 In-Reply-To: <861fe353-eb95-615f-b1dc-3326501342af@android.com> References: <20170608134811.60786-1-andriy.shevchenko@linux.intel.com> <1500400205.25934.27.camel@perches.com> <861fe353-eb95-615f-b1dc-3326501342af@android.com> Organization: Intel Finland Oy Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1375 Lines: 47 On Tue, 2017-07-18 at 12:57 -0700, Mark Salyzyn wrote: > On 07/18/2017 10:50 AM, Joe Perches wrote: > > On Thu, 2017-06-08 at 16:47 +0300, Andy Shevchenko wrote: > > > Recently I have noticed too many users of struct rtc_time that > > > printing > > > its content field by field. > > > > > > In this series I introduce %pt[dt][rv] specifier to make life a > > > bit > > > easier. > > > > Hey Andy. > > > > I just saw a patch with a printk for rtc time from Mark Salyzyn. > > https://lkml.org/lkml/2017/7/18/885 > > > > Any idea if you want to push this extension? > > > > I like the concept and still think it could be extended a bit more. > > > > from: https://lkml.org/lkml/2017/6/8/1134 > > > > My preference would be for %pt[type] > > where is mandatory and could be: > > > >          r for struct rtc_time > >          6 for time64_t > >          k for ktime_t > >          T for struct timespec64 > >          etc > > > > and has an unspecified default of > > YYYY-MM-DD:hh:mm:ss > > > > Perhaps use the "date" formats without the leading > > % uses for for additional styles. > > > > YYYY-MM-DD hh:mm:ss.nnnnnnnnn ? As a separate modifier, yes. See my answer to subthread in patch 4. -- Andy Shevchenko Intel Finland Oy