public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin Garski <mgarski@post.pl>
To: linux-kernel@vger.kernel.org
Subject: Compile warnings in 2.6.14.2 (x86_64)
Date: Sat, 19 Nov 2005 14:19:54 +0100	[thread overview]
Message-ID: <437F267A.9030206@post.pl> (raw)

[Please CC me on replies, I am not subscribed to the list, thanks!]

GCC: gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)
OS: Fedora Core 4 (x86_64)

drivers/md/dm-linear.c: In function ‘linear_ctr’:
drivers/md/dm-linear.c:41: warning: format ‘%lu’ expects type ‘long 
unsigned int *’, but argument 3 has type ‘sector_t *’

drivers/md/dm-linear.c: In function ‘linear_status’:
drivers/md/dm-linear.c:91: warning: format ‘%lu’ expects type ‘long 
unsigned int’, but argument 5 has type ‘sector_t’

drivers/md/dm-stripe.c: In function ‘get_stripe’:
drivers/md/dm-stripe.c:54: warning: format ‘%lu’ expects type ‘long 
unsigned int *’, but argument 3 has type ‘sector_t *’

drivers/md/dm-stripe.c: In function ‘stripe_status’:
drivers/md/dm-stripe.c:198: warning: format ‘%lu’ expects type ‘long 
unsigned int’, but argument 5 has type ‘sector_t’

drivers/md/dm-stripe.c:200: warning: format ‘%lu’ expects type ‘long 
unsigned int’, but argument 5 has type ‘sector_t’

drivers/md/dm-crypt.c: In function ‘crypt_ctr’:
drivers/md/dm-crypt.c:656: warning: format ‘%lu’ expects type ‘long 
unsigned int *’, but argument 3 has type ‘sector_t *’

drivers/md/dm-crypt.c:661: warning: format ‘%lu’ expects type ‘long 
unsigned int *’, but argument 3 has type ‘sector_t *’

drivers/md/dm-crypt.c: In function ‘crypt_status’:
drivers/md/dm-crypt.c:903: warning: format ‘%lu’ expects type ‘long 
unsigned int’, but argument 4 has type ‘sector_t’

drivers/md/dm-crypt.c:903: warning: format ‘%lu’ expects type ‘long 
unsigned int’, but argument 6 has type ‘sector_t’

drivers/usb/input/yealink.c: In function ‘usb_probe’:
drivers/usb/input/yealink.c:909: warning: format ‘%d’ expects type 
‘int’, but argument 4 has type ‘long unsigned int’

lib/ts_kmp.c:125: warning: initialization from incompatible pointer type

lib/ts_bm.c:165: warning: initialization from incompatible pointer type

lib/ts_fsm.c:318: warning: initialization from incompatible pointer type
-- 
Marcin Garski

                 reply	other threads:[~2005-11-19 13:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=437F267A.9030206@post.pl \
    --to=mgarski@post.pl \
    --cc=linux-kernel@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