Linux NFS development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: chuck.lever@oracle.com
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] sunrpc: remove dead variable 'rpciod_running'
Date: Sun, 13 May 2007 16:10:07 +0100	[thread overview]
Message-ID: <20070513151007.GA6059@infradead.org> (raw)
In-Reply-To: <20070209200649.GA9686@infradead.org>

On Fri, Feb 09, 2007 at 08:06:49PM +0000, Christoph Hellwig wrote:
> rpciod_running is not used at all, but due to the way DECLARE_MUTEX_LOCKED
> works we don't get a warning for it.

Looks like this one is still not in.  Any chance to send it to Linus
in this merge cycle?

> Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> Index: linux-2.6/net/sunrpc/sched.c
> ===================================================================
> --- linux-2.6.orig/net/sunrpc/sched.c	2007-02-06 15:55:43.000000000 +0100
> +++ linux-2.6/net/sunrpc/sched.c	2007-02-06 15:55:45.000000000 +0100
> @@ -973,8 +973,6 @@
>  	spin_unlock(&rpc_sched_lock);
>  }
>  
> -static DECLARE_MUTEX_LOCKED(rpciod_running);
> -
>  static void rpciod_killall(void)
>  {
>  	unsigned long flags;
---end quoted text---

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2007-05-13 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 20:06 [PATCH] sunrpc: remove dead variable 'rpciod_running' Christoph Hellwig
2007-02-10  0:03 ` Chuck Lever
2007-05-13 15:10 ` Christoph Hellwig [this message]
2007-05-13 19:51   ` Trond Myklebust

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=20070513151007.GA6059@infradead.org \
    --to=hch@infradead.org \
    --cc=chuck.lever@oracle.com \
    --cc=nfs@lists.sourceforge.net \
    /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