public inbox for linux-kernel@vger.kernel.org
 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 warnings after merge of the fsinfo tree
Date: Tue, 4 Aug 2020 17:34:56 +1000	[thread overview]
Message-ID: <20200804173456.01c819ea@canb.auug.org.au> (raw)

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

Hi all,

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

samples/vfs/test-mntinfo.c: In function 'display_mount':
samples/vfs/test-mntinfo.c:146:19: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 3 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
  146 |  printf("%10u %8llx %2x %x %5s %s",
      |               ~~~~^
      |                   |
      |                   long long unsigned int
      |               %8lx
  147 |         info.mnt_id,
  148 |         (info.mnt_attr_changes +
      |         ~~~~~~~~~~~~~~~~~~~~~~~~
  149 |   info.mnt_topology_changes +
      |   ~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                             |
      |                             __u64 {aka long unsigned int}
  150 |   info.mnt_subtree_notifications),
      |   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
samples/vfs/test-fsinfo.c: In function 'dump_fsinfo_generic_mount_all':
samples/vfs/test-fsinfo.c:384:30: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 5 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
  384 |  printf("%5x %5x %12llx %10llu %s\n",
      |                         ~~~~~^
      |                              |
      |                              long long unsigned int
      |                         %10lu
  385 |         r->mnt_id, r->parent_id, (unsigned long long)r->mnt_unique_id,
  386 |         r->mnt_notify_sum, mp);
      |         ~~~~~~~~~~~~~~~~~     
      |          |
      |          __u64 {aka long unsigned int}

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-08-04  7:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-04  7:34 Stephen Rothwell [this message]
2020-08-04  8:10 ` linux-next: build warnings after merge of the fsinfo tree David Howells
  -- strict thread matches above, loose matches on Subject: below --
2020-05-28  8:40 Stephen Rothwell
2020-05-28 10:11 ` Stephen Rothwell
2020-05-28 13:44   ` Christoph Hellwig

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=20200804173456.01c819ea@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