From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [GIT PULL] Please pull NFS client updates
Date: Fri, 20 Feb 2015 08:19:03 -0800 [thread overview]
Message-ID: <20150220161903.GA17874@infradead.org> (raw)
In-Reply-To: <1424448985.3641.1.camel@primarydata.com>
On Fri, Feb 20, 2015 at 08:16:25AM -0800, Trond Myklebust wrote:
> NFS: struct nfs_commit_info.lock must always point to inode->i_lock
Is there any point in even keeping that lock pointer around then?
next prev parent reply other threads:[~2015-02-20 16:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 16:16 [GIT PULL] Please pull NFS client updates Trond Myklebust
2015-02-20 16:19 ` Christoph Hellwig [this message]
2015-02-20 16:22 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2022-12-13 15:35 Trond Myklebust
2022-12-13 18:13 ` pr-tracker-bot
2015-07-02 16:21 Trond Myklebust
2014-06-10 21:42 Trond Myklebust
2014-03-09 16:22 Trond Myklebust
2013-07-11 18:18 Myklebust, Trond
2013-07-08 17:59 Myklebust, Trond
2012-03-22 14:59 Myklebust, Trond
2011-05-29 16:30 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=20150220161903.GA17874@infradead.org \
--to=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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;
as well as URLs for NNTP newsgroup(s).