Re: [PATCH -next] target: fix tfc_io.c printk format warning

From: Randy Dunlap
Date: Thu Jun 16 2011 - 14:36:30 EST


On Mon, 23 May 2011 13:47:24 -0700 Nicholas A. Bellinger wrote:

> On Mon, 2011-05-23 at 11:35 -0700, Randy Dunlap wrote:
> > From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
> >
> > Fix printk format warning:
> >
> > drivers/target/tcm_fc/tfc_io.c:209: warning: format '%x' expects type 'unsigned int', but argument 5 has type 'size_t'
> >
> > Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
> > ---
>
> Hey Randy,
>
> Kiran (CC'ed) was going to include this along with a bugfix patch for
> scsi-misc, but it's probably easier to just change this in linux-next
> now..

Hey Nick,

Is there some way to have this patch merged for linux-next and mainline?

Thanks.

> Signed-off-by: Nicholas A. Bellinger <nab@xxxxxxxxxxxxxxx>
>
> > drivers/target/tcm_fc/tfc_io.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > and please put an entry in the MAINTAINERS file for drivers/target/
> >
>
> <nod>, sending out that patch shortly.
>
> Thanks,
>
> --nab
>
> >
> > --- linux-next-20110523.orig/drivers/target/tcm_fc/tfc_io.c
> > +++ linux-next-20110523/drivers/target/tcm_fc/tfc_io.c
> > @@ -203,7 +203,7 @@ int ft_queue_data_in(struct se_cmd *se_c
> > /* XXX For now, initiator will retry */
> > if (printk_ratelimit())
> > printk(KERN_ERR "%s: Failed to send frame %p, "
> > - "xid <0x%x>, remaining <0x%x>, "
> > + "xid <0x%x>, remaining <0x%zx>, "
> > "lso_max <0x%x>\n",
> > __func__, fp, ep->xid,
> > remaining, lport->lso_max);
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-next" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/