All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>, Sean Christopherson <seanjc@google.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: selftests: Fix __GUEST_ASSERT() format warnings in ARM's arch timer test
Date: Tue, 26 Mar 2024 06:50:06 -0700	[thread overview]
Message-ID: <171146096643.372204.13848070547978765288.b4-ty@linux.dev> (raw)
In-Reply-To: <20240314175116.2366301-1-seanjc@google.com>


On Thu, 14 Mar 2024 10:51:15 -0700, Sean Christopherson wrote:
> Use %x instead of %lx when printing uint32_t variables to fix format
> warnings in ARM's arch timer test.
> 
> aarch64/arch_timer.c: In function ‘guest_run_stage’:
> aarch64/arch_timer.c:138:33: warning: format ‘%lx’ expects argument of type ‘long unsigned int’,
>                              but argument 6 has type ‘uint32_t’ {aka ‘unsigned int’} [-Wformat=]
>   138 |                                 "config_iter + 1 = 0x%lx, irq_iter = 0x%lx.\n"
>       |                                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ......
>   141 |                                 config_iter + 1, irq_iter);
>       |                                 ~~~~~~~~~~~~~~~
>       |                                             |
>       |                                             uint32_t {aka unsigned int}
> 
> [...]

Applied to kvmarm/fixes, thanks!

[1/1] KVM: selftests: Fix __GUEST_ASSERT() format warnings in ARM's arch timer test
      commit: 29b0075ed61cda250449f556fbe007a5c469440c

-- 
Best,
Oliver

WARNING: multiple messages have this Message-ID (diff)
From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>, Sean Christopherson <seanjc@google.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: selftests: Fix __GUEST_ASSERT() format warnings in ARM's arch timer test
Date: Tue, 26 Mar 2024 06:50:06 -0700	[thread overview]
Message-ID: <171146096643.372204.13848070547978765288.b4-ty@linux.dev> (raw)
In-Reply-To: <20240314175116.2366301-1-seanjc@google.com>


On Thu, 14 Mar 2024 10:51:15 -0700, Sean Christopherson wrote:
> Use %x instead of %lx when printing uint32_t variables to fix format
> warnings in ARM's arch timer test.
> 
> aarch64/arch_timer.c: In function ‘guest_run_stage’:
> aarch64/arch_timer.c:138:33: warning: format ‘%lx’ expects argument of type ‘long unsigned int’,
>                              but argument 6 has type ‘uint32_t’ {aka ‘unsigned int’} [-Wformat=]
>   138 |                                 "config_iter + 1 = 0x%lx, irq_iter = 0x%lx.\n"
>       |                                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ......
>   141 |                                 config_iter + 1, irq_iter);
>       |                                 ~~~~~~~~~~~~~~~
>       |                                             |
>       |                                             uint32_t {aka unsigned int}
> 
> [...]

Applied to kvmarm/fixes, thanks!

[1/1] KVM: selftests: Fix __GUEST_ASSERT() format warnings in ARM's arch timer test
      commit: 29b0075ed61cda250449f556fbe007a5c469440c

-- 
Best,
Oliver

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-03-26 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 17:51 [PATCH] KVM: selftests: Fix __GUEST_ASSERT() format warnings in ARM's arch timer test Sean Christopherson
2024-03-14 17:51 ` Sean Christopherson
2024-03-26 13:50 ` Oliver Upton [this message]
2024-03-26 13:50   ` Oliver Upton

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=171146096643.372204.13848070547978765288.b4-ty@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=seanjc@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.