mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Howells <dhowells@redhat.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warning after merge of the fsinfo tree
Date: Tue, 12 May 2020 20:22:26 +1000	[thread overview]
Message-ID: <20200512202226.79191a47@canb.auug.org.au> (raw)

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

Hi all,

After merging the fsinfo tree, today's linux-next build (powerpc
allyesconfig) produced this warning:

samples/watch_queue/watch_test.c: In function 'saw_super_change':
samples/watch_queue/watch_test.c:107:21: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
  107 |  printf("SUPER %08llx change=%u[%s]\n",
      |                ~~~~~^
      |                     |
      |                     long long unsigned int
      |                %08lx
  108 |         s->sb_id, n->subtype, super_subtypes[n->subtype]);
      |         ~~~~~~~~     
      |          |
      |          __u64 {aka long unsigned int}

Introduced by commit

  6e1617461ab8 ("watch_queue: sample: Display superblock notifications")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2020-05-12 10:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 10:22 Stephen Rothwell [this message]
2020-05-12 23:27 ` David Howells
2020-05-14  9:10 Stephen Rothwell

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=20200512202226.79191a47@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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

all inboxes | Powered by JetHome®