[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <160805599050.14591.5854311082825914383@build.alporthouse.com>
Date: Tue, 15 Dec 2020 18:13:10 +0000
From: Chris Wilson <chris@...is-wilson.co.uk>
To: airlied@...ux.ie, daniel@...ll.ch, daniele.ceraolospurio@...el.com,
jani.nikula@...ux.intel.com, joonas.lahtinen@...ux.intel.com,
lionel.g.landwerlin@...el.com, rodrigo.vivi@...el.com,
tejaskumarx.surendrakumar.upadhyay@...el.com, trix@...hat.com,
tvrtko.ursulin@...el.com, venkata.s.dhanalakota@...el.com
Cc: intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, Tom Rix <trix@...hat.com>
Subject: Re: [PATCH] drm/i915: remove h from printk format specifier
Quoting trix@...hat.com (2020-12-15 14:41:01)
> From: Tom Rix <trix@...hat.com>
>
> See Documentation/core-api/printk-formats.rst.
> h should no longer be used in the format specifier for printk.
It's understood by format_decode().
* 'h', 'l', or 'L' for integer fields
At least reference commit cbacb5ab0aa0 ("docs: printk-formats: Stop
encouraging use of unnecessary %h[xudi] and %hh[xudi]") as to why the
printk-formats.rst was altered so we know the code is merely in bad
taste and not using undefined behaviour of printk.
-Chris
Powered by blists - more mailing lists