From: Christoph Hellwig <hch@infradead.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Jeff Layton <jlayton@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] please pull file locking changes for v3.15 (pile #2)
Date: Fri, 25 Apr 2014 03:35:37 -0700 [thread overview]
Message-ID: <20140425103537.GA10757@infradead.org> (raw)
In-Reply-To: <20140425095739.GB22295@fieldses.org>
On Fri, Apr 25, 2014 at 05:57:39AM -0400, J. Bruce Fields wrote:
> > Jeff Layton (3):
> > locks: allow __break_lease to sleep even when break_time is 0
> > locks: rename file-private locks to "open file description locks"
>
> Nit: they're "descriptors", not "descriptions".
No, in this case they are not.
next prev parent reply other threads:[~2014-04-25 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 11:45 [GIT PULL] please pull file locking changes for v3.15 (pile #2) Jeff Layton
2014-04-25 9:57 ` J. Bruce Fields
2014-04-25 10:01 ` J. Bruce Fields
2014-04-25 10:35 ` Christoph Hellwig [this message]
2014-04-25 10:39 ` Jeff Layton
2014-04-26 16:46 ` 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=20140425103537.GA10757@infradead.org \
--to=hch@infradead.org \
--cc=bfields@fieldses.org \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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).