From: Doug Anderson <dianders@chromium.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Petr Mladek <pmladek@suse.com>, JC Kuo <jckuo@nvidia.com>,
Joe Perches <joe@perches.com>, Sumit Garg <sumit.garg@linaro.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux USB List <linux-usb@vger.kernel.org>,
linux-tegra@vger.kernel.org, linux-nilfs@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Jonathan Corbet <corbet@lwn.net>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Ryusuke Konishi <konishi.ryusuke@gmail.com>,
Jason Wessel <jason.wessel@windriver.com>,
Daniel Thompson <daniel.thompson@linaro.org>
Subject: Re: [PATCH v1 2/4] kdb: Switch to use %ptTs
Date: Mon, 10 May 2021 17:05:46 -0700 [thread overview]
Message-ID: <CAD=FV=VpuyYBv2tj5AHLx7U7vfCpH1A6hfG_amscZ6OupRwEHg@mail.gmail.com> (raw)
In-Reply-To: <20210510150413.59356-2-andriy.shevchenko@linux.intel.com>
Hi,
On Mon, May 10, 2021 at 8:04 AM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> Use %ptTs instead of open-coded variant to print contents
> of time64_t type in human readable form.
>
> Cc: Jason Wessel <jason.wessel@windriver.com>
> Cc: Daniel Thompson <daniel.thompson@linaro.org>
> Cc: kgdb-bugreport@lists.sourceforge.net
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> kernel/debug/kdb/kdb_main.c | 9 +--------
> 1 file changed, 1 insertion(+), 8 deletions(-)
I kinda doubt anyone would really care if we just switched kdb to just
the old "%ptT". Probably no machines are parsing this string.
...but in any case, now that the nifty new format is there we might as
well use it. Thus:
Reviewed-by: Douglas Anderson <dianders@chromium.org>
next prev parent reply other threads:[~2021-05-11 0:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 15:04 [PATCH v1 1/4] lib/vsprintf: Allow to override date and time separator Andy Shevchenko
2021-05-10 15:04 ` [PATCH v1 2/4] kdb: Switch to use %ptTs Andy Shevchenko
2021-05-11 0:05 ` Doug Anderson [this message]
2021-05-11 7:14 ` Andy Shevchenko
2021-05-11 14:16 ` Petr Mladek
2021-05-10 15:04 ` [PATCH v1 3/4] nilfs2: " Andy Shevchenko
2021-05-11 14:16 ` Petr Mladek
2021-05-10 15:04 ` [PATCH v1 4/4] usb: host: xhci-tegra: " Andy Shevchenko
2021-05-11 14:16 ` Petr Mladek
2021-05-11 14:14 ` [PATCH v1 1/4] lib/vsprintf: Allow to override date and time separator Petr Mladek
2021-05-11 14:56 ` Andy Shevchenko
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='CAD=FV=VpuyYBv2tj5AHLx7U7vfCpH1A6hfG_amscZ6OupRwEHg@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=daniel.thompson@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jason.wessel@windriver.com \
--cc=jckuo@nvidia.com \
--cc=joe@perches.com \
--cc=jonathanh@nvidia.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mathias.nyman@intel.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=sumit.garg@linaro.org \
--cc=thierry.reding@gmail.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).