All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Heiko Thiery <heiko.thiery@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] Fix warning due to format mismatch for field width argument to fprintf()
Date: Sun, 16 May 2021 22:40:09 +0200	[thread overview]
Message-ID: <df0269f3bae01c37a7dbeaa4a8bb4b3fd0277d24.camel@decadent.org.uk> (raw)
In-Reply-To: <CAEyMn7ap3RL_oh0ucerH9POP+S4VGKfULhJQSb3AVeNFjR4VZw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1967 bytes --]

On Sun, 2021-05-16 at 20:11 +0200, Heiko Thiery wrote:
> Hi all,
> 
> Am Sa., 15. Mai 2021 um 09:59 Uhr schrieb Heiko Thiery <heiko.thiery@gmail.com>:
> > 
> > Added Ben's other mail addresses.
> > 
> > Am Sa., 15. Mai 2021 um 08:49 Uhr schrieb Heiko Thiery <heiko.thiery@gmail.com>:
> > > 
> > > bnxt.c:66:54: warning: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘unsigned int’ [-Wformat=]
> > >    66 |   fprintf(stdout, "Length is too short, expected 0x%lx\n",
> > >       |                                                    ~~^
> > >       |                                                      |
> > >       |                                                      long unsigned int
> > >       |                                                    %x
> > > 
> > > Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
> > > ---
> > >  bnxt.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/bnxt.c b/bnxt.c
> > > index b46db72..0c62d1e 100644
> > > --- a/bnxt.c
> > > +++ b/bnxt.c
> > > @@ -63,7 +63,7 @@ int bnxt_dump_regs(struct ethtool_drvinfo *info __maybe_unused, struct ethtool_r
> > >                 return 0;
> > > 
> > >         if (regs->len < (BNXT_PXP_REG_LEN + BNXT_PCIE_STATS_LEN)) {
> > > -               fprintf(stdout, "Length is too short, expected 0x%lx\n",
> > > +               fprintf(stdout, "Length is too short, expected 0x%x\n",
> > >                         BNXT_PXP_REG_LEN + BNXT_PCIE_STATS_LEN);
> 
> This does not solve the issue. The provided patch only works on 32bit
> systems. It seems there is a problem with 32bit vs 64bit.

It looks like the type of BNXT_PXP_REG_LEN + BNXT_PCIE_STATS_LEN will
be size_t, so the correct format is "%zx".

Ben.

-- 
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-05-16 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15  6:49 [PATCH] Fix warning due to format mismatch for field width argument to fprintf() Heiko Thiery
2021-05-15  7:59 ` Heiko Thiery
2021-05-16 18:11   ` Heiko Thiery
2021-05-16 20:40     ` Ben Hutchings [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=df0269f3bae01c37a7dbeaa4a8bb4b3fd0277d24.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=heiko.thiery@gmail.com \
    --cc=netdev@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 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.