[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a1-Fpkg-d0k9HryqW4ULVfZPL6_McLxoFbUT6CTmMoMFg@mail.gmail.com>
Date: Mon, 27 Mar 2017 17:35:13 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Paul Menzel <pmenzel@...gen.mpg.de>, Len Brown <lenb@...nel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
Borislav Petkov <bp@...en8.de>,
"Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe
On Mon, Mar 27, 2017 at 5:30 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Mon, 27 Mar 2017 16:53:09 +0200
>> We could probably introduce a %pts format string for timespec64
>> and have that pretty-printed.
>
> Hmm, probably don't want a %p as that suggests its a pointer, which it
> should not be. Unless we pass in the address of the number.
The special format strings that the kernel defines all start with %p and
require passing by reference so we don't get a warning from gcc. We can't
just make up new format strings otherwise, but we can create new meaning
for special pointers as we do for struct resource and others.
Arnd
Powered by blists - more mailing lists