From: Christoph Hellwig <hch@infradead.org>
To: Josh Triplett <josht@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
nfs@lists.sourceforge.net, Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: [NFS] [PATCH] [nfsd] Add lock annotations to e_start and e_stop
Date: Wed, 26 Jul 2006 09:06:56 +0100 [thread overview]
Message-ID: <20060726080656.GA28346@infradead.org> (raw)
In-Reply-To: <1153840824.12517.9.camel@josh-work.beaverton.ibm.com>
On Tue, Jul 25, 2006 at 08:20:24AM -0700, Josh Triplett wrote:
> e_start acquires svc_export_cache.hash_lock, and e_stop releases it. Add lock
> annotations to these two functions so that sparse can check callers for lock
> pairing, and so that sparse will not complain about these functions since they
> intentionally use locks in this manner.
>
> Signed-off-by: Josh Triplett <josh@freedesktop.org>
The Signed-off-by: line doesn't match the from line of this mail. Is that
any problem or fine in general?
next prev parent reply other threads:[~2006-07-26 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 15:20 Josh Triplett
2006-07-26 8:06 ` Christoph Hellwig [this message]
2006-07-26 8:19 ` [NFS] " Arjan van de Ven
2006-07-26 15:42 ` Josh Triplett
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=20060726080656.GA28346@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=josht@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--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
all inboxes | Powered by JetHome®