On Tue, Dec 15, 2020 at 10:11 AM Christian König
wrote:
>
> Am 15.12.20 um 16:06 schrieb Tom Rix:
> > On 12/15/20 6:47 AM, Christian König wrote:
> >> Am 15.12.20 um 15:38 schrieb t...@redhat.com:
> >>> From: Tom Rix
> >>>
> >>> See Documentation/core-api/printk-formats.rst.
> >>> h should no lon
Am 15.12.20 um 16:06 schrieb Tom Rix:
On 12/15/20 6:47 AM, Christian König wrote:
Am 15.12.20 um 15:38 schrieb t...@redhat.com:
From: Tom Rix
See Documentation/core-api/printk-formats.rst.
h should no longer be used in the format specifier for printk.
In general looks valid to me, but my que
On 12/15/20 6:47 AM, Christian König wrote:
> Am 15.12.20 um 15:38 schrieb t...@redhat.com:
>> From: Tom Rix
>>
>> See Documentation/core-api/printk-formats.rst.
>> h should no longer be used in the format specifier for printk.
>
> In general looks valid to me, but my question is how does that wo
Am 15.12.20 um 15:38 schrieb t...@redhat.com:
From: Tom Rix
See Documentation/core-api/printk-formats.rst.
h should no longer be used in the format specifier for printk.
In general looks valid to me, but my question is how does that work?
I mean we specify h here because it is a short int. A
