From: Carlos Bilbao <carlos.bilbao@amd.com>
To: Tejun Heo <tj@kernel.org>
Cc: josef@toxicpanda.com, axboe@kernel.dk, cgroups@vger.kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
amd <amd@localhost.localdomain>
Subject: Re: [PATCH] blk-iocost: fix seq_printf compile type mismatch error
Date: Mon, 31 Jul 2023 10:04:14 -0500 [thread overview]
Message-ID: <7f451eb2-6e62-9e49-c47a-e0de59cc7ebf@amd.com> (raw)
In-Reply-To: <ZLstYbAzqkqwIRzy@slm.duckdns.org>
On 7/21/23 20:14, Tejun Heo wrote:
> On Fri, Jul 21, 2023 at 05:32:04PM -0500, Carlos Bilbao wrote:
>> On 7/17/23 9:18 AM, Carlos Bilbao wrote:
>>> From: amd <amd@localhost.localdomain>
>>>
>>> Fix two type mismatch errors encountered while compiling blk-iocost.c with
>>> GCC version 13.1.1 that involved constant operator WEIGHT_ONE. Cast the
>>> result of the division operation to (unsigned int) to match the expected
>>> format specifier %u in two seq_printf invocations.
>>>
>>> Reviewed-by: Carlos Bilbao <carlos.bilbao@amd.com>
>> This should have been:
>>
>> Signed-off-by: Carlos Bilbao <carlos.bilbao@amd.com>
>
> Carlos, can you please retest the current linus#master?
>
Yes, that version compiled successfully without changes in my compiler. The
kernel that gave me said error was a custom v6.1.0-rc4 (Obtained from:
https://github.com/coconut-svsm/linux/tree/svsm-host)
> Thanks.
>
Thanks,
Carlos
prev parent reply other threads:[~2023-07-31 15:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230717141852.153965-1-carlos.bilbao@amd.com>
2023-07-17 14:23 ` [PATCH] blk-iocost: fix seq_printf compile type mismatch error Carlos Bilbao
2023-07-17 18:49 ` Tejun Heo
2023-07-18 15:37 ` Carlos Bilbao
2023-07-20 20:05 ` Tejun Heo
2023-07-19 8:57 ` David Laight
2023-07-20 20:06 ` 'Tejun Heo'
2023-07-21 8:05 ` David Laight
2023-07-21 17:58 ` 'Tejun Heo'
2023-07-21 22:32 ` Carlos Bilbao
2023-07-22 1:14 ` Tejun Heo
2023-07-31 15:04 ` Carlos Bilbao [this message]
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=7f451eb2-6e62-9e49-c47a-e0de59cc7ebf@amd.com \
--to=carlos.bilbao@amd.com \
--cc=amd@localhost.localdomain \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/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