public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Steve Dickson <SteveD@RedHat.com>
Cc: linux-nfs@vger.kernel.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>
Subject: [nfs-utils PATCH 3/3] support: nfs: rpc_socket: silence unused parameter warning on salen
Date: Mon, 13 Jan 2020 17:29:18 +0100	[thread overview]
Message-ID: <20200113162918.77144-4-giulio.benetti@benettiengineering.com> (raw)
In-Reply-To: <20200113162918.77144-1-giulio.benetti@benettiengineering.com>

If HAVE_LIBTIRPC is not defined salen parameter is unused and not taken
into account, so compiler emits warning. Add a (void) salen; in that
case.

Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
---
 support/nfs/rpc_socket.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/support/nfs/rpc_socket.c b/support/nfs/rpc_socket.c
index bdf6d2f6..5fabf5a1 100644
--- a/support/nfs/rpc_socket.c
+++ b/support/nfs/rpc_socket.c
@@ -77,6 +77,8 @@ static CLIENT *nfs_get_localclient(const struct sockaddr *sap,
 		.len		= (size_t)salen,
 		.buf		= &address,
 	};
+#else
+	(void) salen;
 #endif	/* HAVE_LIBTIRPC */
 	CLIENT *client;
 	int sock;
-- 
2.20.1


  parent reply	other threads:[~2020-01-13 16:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 16:29 [nfs-utils PATCH 0/3] bump rpcgen version and silence some warning Giulio Benetti
2020-01-13 16:29 ` [nfs-utils PATCH 2/3] rpcgen: rpc_cout: silence format-nonliteral Giulio Benetti
2020-01-13 16:29 ` Giulio Benetti [this message]
2020-01-16 20:37 ` [nfs-utils PATCH 0/3] bump rpcgen version and silence some warning Steve Dickson
2020-01-16 20:41   ` Giulio Benetti
2020-01-16 20:44     ` Giulio Benetti
2020-01-16 21:08       ` Steve Dickson
2020-01-17  6:30         ` Petr Vorel
2020-01-17 14:32           ` Steve Dickson
2020-01-19 18:45             ` Petr Vorel

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=20200113162918.77144-4-giulio.benetti@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=SteveD@RedHat.com \
    --cc=linux-nfs@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