From: Christoph Hellwig <hch@infradead.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: nfsd fixes for 2.6.30
Date: Tue, 12 May 2009 16:15:26 -0400 [thread overview]
Message-ID: <20090512201526.GA20972@infradead.org> (raw)
In-Reply-To: <20090512192912.GH19164@fieldses.org>
On Tue, May 12, 2009 at 03:29:12PM -0400, J. Bruce Fields wrote:
> The following nfsd fixes are available from the for-2.6.30 branch at:
>
> git://linux-nfs.org/~bfields/linux.git for-2.6.30
>
> (Note: I wasn't sure of the last one, "nfsd: silence lockdep warning":
> on the one hand, it's just a warning. On the other hand, a lot of users
> may assume it's something more serious and freak out, just because
> there's a backtrace in it. Should this have been saved for the next
> merge window?)
I think it's fine. For non-lockdep builds the annotation doesn't change
anything, and for lockdep builds it fixes the false positive.
next prev parent reply other threads:[~2009-05-12 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 19:29 nfsd fixes for 2.6.30 J. Bruce Fields
2009-05-12 20:15 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-28 21:52 J. Bruce Fields
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=20090512201526.GA20972@infradead.org \
--to=hch@infradead.org \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.