linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] VFS pile 1 - misc bits
Date: Thu, 24 Sep 2009 10:57:27 -0700	[thread overview]
Message-ID: <ada4oqs2pko.fsf@cisco.com> (raw)
In-Reply-To: <20090924143242.GO14381@ZenIV.linux.org.uk> (Al Viro's message of "Thu, 24 Sep 2009 15:32:42 +0100")

The patch in <http://lkml.org/lkml/2009/7/14/309> (add lockdep
annotation to s_vfs_rename_mutex to avoid lockdep spew with rename on
ecryptfs) seems to have been dropped -- or maybe it is just down in the
queue somewhere.  I did see Andrew send it to you again a week or so
back.

Thanks,
  Roland

      reply	other threads:[~2009-09-24 17:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 14:32 [git pull] VFS pile 1 - misc bits Al Viro
2009-09-24 17:57 ` Roland Dreier [this message]

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=ada4oqs2pko.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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).