public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: ixp4xx: fix read{b,w,l} return types
Date: Tue, 01 Dec 2015 23:46:03 +0100	[thread overview]
Message-ID: <4900418.HEVAcnQtkC@wuerfel> (raw)
In-Reply-To: <m3h9kaz2ej.fsf@t19.piap.pl>

On Wednesday 25 November 2015 13:31:16 Krzysztof Ha?asa wrote:
> Arnd Bergmann <arnd@arndb.de> writes:
> 
> > On ixp4xx, the readl() function returns an 'unsigned long' output
> > when indirect I/O is used. This is unlike any other platform, and
> > it causes lots of harmless compiler warnings, such as:
> >
> > drivers/ata/libahci.c: In function 'ahci_show_host_version':
> > drivers/ata/libahci.c:254:22: warning: format '%x' expects argument of type 'unsigned int', but argument 3 has type 'long unsigned int' [-Wformat=]
> > drivers/block/mtip32xx/mtip32xx.c: In function 'mtip_hw_read_registers':
> > drivers/block/mtip32xx/mtip32xx.c:2602:31: warning: format '%X' expects argument of type 'unsigned int', but argument 3 has type 'long unsigned int' [-Wformat=]
> > drivers/block/cciss.c: In function 'print_cfg_table':
> > drivers/block/cciss.c:3845:25: warning: format '%d' expects argument of type 'int', but argument 4 has type 'long unsigned int' [-Wformat=]
> >
> > This changes all six of the ixp4xx specific I/O read functions
> > to return the same types that we have in the normal asm/io.h,
> > to avoid the warnings.
> 
> Thanks for fixing this.
> 
> Acked-by: Krzysztof Halasa <khalasa@piap.pl>
> 

Applied to fixes for 4.4 now with your ack.

  reply	other threads:[~2015-12-01 22:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 22:20 [PATCH] ARM: ixp4xx: fix read{b,w,l} return types Arnd Bergmann
2015-11-25 12:31 ` Krzysztof Hałasa
2015-12-01 22:46   ` Arnd Bergmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-23 13:54 Arnd Bergmann

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=4900418.HEVAcnQtkC@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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