Netdev List
 help / color / mirror / Atom feed
From: "Longchamp, Valentin" <Valentin.Longchamp@keymile.com>
To: "christophe.leroy@c-s.fr" <christophe.leroy@c-s.fr>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"leoli@freescale.com" <leoli@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] net/ethernet/freescale: fix warning for ucc_geth
Date: Thu, 14 Sep 2017 14:17:42 +0000	[thread overview]
Message-ID: <1505398677.19702.6.camel@keymile.com> (raw)
In-Reply-To: <f5c5c526-99d4-ff3d-1e2a-23d71bcafa4b@c-s.fr>

Hi Christophe,

On Thu, 2017-09-14 at 15:24 +0200, Christophe LEROY wrote:
> Hi,
> 
> Le 14/09/2017 à 14:05, Valentin Longchamp a écrit :
> > Simple printk format warning for the the ucc registers address.
> 
> Did you test your patch with mpc83xx_defconfig ?

No I only tested on a 85xx where I had another (similar, because the
physical addresses are u64 and not u32) warning.

My quick fix indeed did not take the different typedefs for
phys_addr_t.

I try to come with a v2 that covers this.

Thanks for the feedback.

Valentin
> 
> I get a new warning with your patch:
> 
>    CC      drivers/net/ethernet/freescale/ucc_geth.o
> In file included from ./include/linux/printk.h:6:0,
>                   from ./include/linux/kernel.h:13,
>                   from drivers/net/ethernet/freescale/ucc_geth.c:18:
> drivers/net/ethernet/freescale/ucc_geth.c: In function
> ‘ucc_geth_probe’:
> ./include/linux/kern_levels.h:4:18: warning: format ‘%llx’ expects 
> argument of type ‘long long unsigned int’, but argument 3 has type 
> ‘resource_size_t {aka unsigned int}’ [-Wformat=]
>   #define KERN_SOH "\001"  /* ASCII Start Of Header */
>                    ^
> ./include/linux/kern_levels.h:13:19: note: in expansion of macro
> ‘KERN_SOH’
>   #define KERN_INFO KERN_SOH "6" /* informational */
>                     ^
> ./include/linux/printk.h:308:9: note: in expansion of macro
> ‘KERN_INFO’
>    printk(KERN_INFO pr_fmt(fmt), ##__VA_ARGS__)
>           ^
> drivers/net/ethernet/freescale/ucc_geth.c:3860:3: note: in expansion
> of 
> macro ‘pr_info’
>     pr_info("UCC%1d at 0x%8llx (irq = %d)\n",
>     ^
> 
> Christophe
> 
> > 
> > Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com>
> > ---
> >   drivers/net/ethernet/freescale/ucc_geth.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/net/ethernet/freescale/ucc_geth.c
> > b/drivers/net/ethernet/freescale/ucc_geth.c
> > index f77ba9fa257b..56b8fdb35c3b 100644
> > --- a/drivers/net/ethernet/freescale/ucc_geth.c
> > +++ b/drivers/net/ethernet/freescale/ucc_geth.c
> > @@ -3857,7 +3857,7 @@ static int ucc_geth_probe(struct
> > platform_device* ofdev)
> >   	}
> >   
> >   	if (netif_msg_probe(&debug))
> > -		pr_info("UCC%1d at 0x%8x (irq = %d)\n",
> > +		pr_info("UCC%1d at 0x%8llx (irq = %d)\n",
> >   			ug_info->uf_info.ucc_num + 1, ug_info-
> > >uf_info.regs,
> >   			ug_info->uf_info.irq);
> >   
> > 

      reply	other threads:[~2017-09-14 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14 12:05 [PATCH] net/ethernet/freescale: fix warning for ucc_geth Valentin Longchamp
2017-09-14 13:24 ` Christophe LEROY
2017-09-14 14:17   ` Longchamp, Valentin [this message]

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=1505398677.19702.6.camel@keymile.com \
    --to=valentin.longchamp@keymile.com \
    --cc=christophe.leroy@c-s.fr \
    --cc=leoli@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=netdev@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