From: Jeff Layton <jlayton@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] sunrpc: fix build-time warning
Date: Thu, 31 Dec 2009 20:54:54 -0500 [thread overview]
Message-ID: <20091231205454.0f84f091@tupile.poochiereds.net> (raw)
In-Reply-To: <20091231091815.a1ea7e51.rdunlap@xenotime.net>
On Thu, 31 Dec 2009 09:18:15 -0800
Randy Dunlap <rdunlap@xenotime.net> wrote:
> On Wed, 30 Dec 2009 21:23:15 -0500 Jeff Layton wrote:
>
> > Commit 486bad2e40e938cd68fd853b7a9fa3115a9d3a4a introduced this warning
> > at build time on some 32-bit architectures:
> >
> > net/sunrpc/auth_gss/auth_gss.c: In function 'gss_pipe_downcall':
> > net/sunrpc/auth_gss/auth_gss.c:660: warning: format '%ld' expects type 'long int', but argument 3 has type 'ssize_t
> >
> > ...fix it by changing the length modifier in the printk.
> >
> > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > Signed-off-by: Jeff Layton <jlayton@redhat.com>
> > ---
> > net/sunrpc/auth_gss/auth_gss.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/net/sunrpc/auth_gss/auth_gss.c b/net/sunrpc/auth_gss/auth_gss.c
> > index 66cb89c..6de4f91 100644
> > --- a/net/sunrpc/auth_gss/auth_gss.c
> > +++ b/net/sunrpc/auth_gss/auth_gss.c
> > @@ -657,7 +657,7 @@ gss_pipe_downcall(struct file *filp, const char __user *src, size_t mlen)
> > break;
> > default:
> > printk(KERN_CRIT "%s: bad return from "
> > - "gss_fill_context: %ld\n", __func__, err);
> > + "gss_fill_context: %Zd\n", __func__, err);
> > BUG();
> > }
> > goto err_release_msg;
> > --
>
> I have that almost-same patch in my (unposted) linux-next patch queue,
> so basically, ack, except that we try to use 'z' instead of 'Z' nowadays.
>
> My quick kernel source tree count is 173 %Z to 966 %z.
> (Please don't anyone start a project of converting %Z to %z.)
>
If you have a patch queued up for this with the preferred qualifier,
then I'm fine with dropping this one.
Cheers,
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2010-01-01 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 2:23 Jeff Layton
2009-12-31 17:18 ` Randy Dunlap
2010-01-01 1:54 ` Jeff Layton [this message]
2010-01-02 2:25 ` [PATCH v2] " Randy Dunlap
2010-01-03 11:51 ` Jeff Layton
2010-01-06 23:10 ` Trond Myklebust
2010-01-06 23:51 ` 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=20091231205454.0f84f091@tupile.poochiereds.net \
--to=jlayton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
--cc=trond.myklebust@fys.uio.no \
/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
all inboxes | Powered by JetHome®