public inbox for cgroups@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Bilbao <carlos.bilbao-5C7GfCeVMHo@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: josef-DigfWCa+lFGyeJad7bwFQA@public.gmane.org,
	axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	amd <amd-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
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-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.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-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
>>>
>>> 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-5C7GfCeVMHo@public.gmane.org>
>> This should have been:
>>
>> Signed-off-by: Carlos Bilbao <carlos.bilbao-5C7GfCeVMHo@public.gmane.org>
> 
> 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

      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>
     [not found] ` <20230717141852.153965-1-carlos.bilbao-5C7GfCeVMHo@public.gmane.org>
2023-07-17 14:23   ` [PATCH] blk-iocost: fix seq_printf compile type mismatch error Carlos Bilbao
2023-07-17 18:49   ` Tejun Heo
     [not found]     ` <ZLWNHuTGk0fy8pjE-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2023-07-18 15:37       ` Carlos Bilbao
2023-07-20 20:05         ` Tejun Heo
2023-07-19  8:57     ` David Laight
     [not found]       ` <2b4540aadc3c4449a192aeed6211f232-1XygrNkDbNvwg4NCKwmqgw@public.gmane.org>
2023-07-20 20:06         ` 'Tejun Heo'
2023-07-21  8:05           ` David Laight
     [not found]             ` <fd89f72848da4569a19ec8a1ac9ec94e-1XygrNkDbNvwg4NCKwmqgw@public.gmane.org>
2023-07-21 17:58               ` 'Tejun Heo'
2023-07-21 22:32 ` Carlos Bilbao
     [not found]   ` <93557f79-c12c-3c3f-2c25-9ba50a618daa-5C7GfCeVMHo@public.gmane.org>
2023-07-22  1:14     ` Tejun Heo
     [not found]       ` <ZLstYbAzqkqwIRzy-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
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-5c7gfcevmho@public.gmane.org \
    --cc=amd-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org \
    --cc=axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=josef-DigfWCa+lFGyeJad7bwFQA@public.gmane.org \
    --cc=linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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