All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jeff Layton <jlayton@redhat.com>
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: [PATCH v2] sunrpc: fix build-time warning
Date: Fri, 1 Jan 2010 18:25:14 -0800	[thread overview]
Message-ID: <20100101182514.cb1f49ef.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091231205454.0f84f091-PC62bkCOHzGdMjc06nkz3ljfA9RmPOcC@public.gmane.org>

From: Randy Dunlap <randy.dunlap@oracle.com>

Fix auth_gss printk format warning:

net/sunrpc/auth_gss/auth_gss.c:660: warning: format '%ld' expects type 'long int', but argument 3 has type 'ssize_t'

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 net/sunrpc/auth_gss/auth_gss.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-next-20091229.orig/net/sunrpc/auth_gss/auth_gss.c
+++ linux-next-20091229/net/sunrpc/auth_gss/auth_gss.c
@@ -657,7 +657,7 @@ gss_pipe_downcall(struct file *filp, con
 			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;
---

WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jeff Layton <jlayton@redhat.com>
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: [PATCH v2] sunrpc: fix build-time warning
Date: Fri, 1 Jan 2010 18:25:14 -0800	[thread overview]
Message-ID: <20100101182514.cb1f49ef.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091231205454.0f84f091@tupile.poochiereds.net>

From: Randy Dunlap <randy.dunlap@oracle.com>

Fix auth_gss printk format warning:

net/sunrpc/auth_gss/auth_gss.c:660: warning: format '%ld' expects type 'long int', but argument 3 has type 'ssize_t'

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 net/sunrpc/auth_gss/auth_gss.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-next-20091229.orig/net/sunrpc/auth_gss/auth_gss.c
+++ linux-next-20091229/net/sunrpc/auth_gss/auth_gss.c
@@ -657,7 +657,7 @@ gss_pipe_downcall(struct file *filp, con
 			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;
---

  parent reply	other threads:[~2010-01-02  2:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-31  2:23 [PATCH] sunrpc: fix build-time warning Jeff Layton
2009-12-31 17:18 ` Randy Dunlap
2010-01-01  1:54   ` Jeff Layton
     [not found]     ` <20091231205454.0f84f091-PC62bkCOHzGdMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2010-01-02  2:25       ` Randy Dunlap [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
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=20100101182514.cb1f49ef.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=jlayton@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.