From: Tejun Heo <tj@kernel.org>
To: Carlos Bilbao <carlos.bilbao@amd.com>
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: Fri, 21 Jul 2023 15:14:09 -1000 [thread overview]
Message-ID: <ZLstYbAzqkqwIRzy@slm.duckdns.org> (raw)
In-Reply-To: <93557f79-c12c-3c3f-2c25-9ba50a618daa@amd.com>
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?
Thanks.
--
tejun
next prev parent reply other threads:[~2023-07-22 1:14 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 [this message]
2023-07-31 15:04 ` Carlos Bilbao
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=ZLstYbAzqkqwIRzy@slm.duckdns.org \
--to=tj@kernel.org \
--cc=amd@localhost.localdomain \
--cc=axboe@kernel.dk \
--cc=carlos.bilbao@amd.com \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).