public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Theodore Ts'o <tytso@mit•edu>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: ext4 tree build warning
Date: Tue, 16 Jun 2009 11:08:44 +1000	[thread overview]
Message-ID: <20090616110844.65254bc8.sfr@canb.auug.org.au> (raw)

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

Hi Ted,

Today's linux-next build (powerpc ppc64_defconfig) produced this warning:

In file included from include/trace/ftrace.h:262,
                 from include/trace/define_trace.h:57,
                 from include/trace/events/ext4.h:720,
                 from fs/ext4/super.c:51:
include/trace/events/ext4.h: In function 'ftrace_raw_output_ext4_free_inode':
include/trace/events/ext4.h:12: warning: format '%llu' expects type 'long long unsigned int', but argument 8 has type 'blkcnt_t'

Introduced by commit a6e130e94db16b324fbf2eeed2b310273625acf7 ("ext4:
convert instrumentation from markers to tracepoints").

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-06-16  1:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  1:08 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-02  1:26 linux-next: ext4 tree build warning Stephen Rothwell
2009-10-03  1:03 ` Theodore Tso
2009-08-27  7:17 Stephen Rothwell
2009-08-28 13:50 ` Theodore Tso
2009-06-09  0:54 Stephen Rothwell
2009-06-09  4:23 ` Theodore Tso
2009-06-09  7:11   ` Stephen Rothwell
2009-03-30  4:48 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=20090616110844.65254bc8.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tytso@mit$(echo .)edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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