From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Merge of the 'write_inode' branch from the VFS tree
Date: Fri, 05 Mar 2010 10:26:40 -0500 [thread overview]
Message-ID: <1267802800.5174.6.camel@localhost.localdomain> (raw)
Hi Al,
When you submitted the VFS changes for this merge window, I was hoping
you would include the 'write_inode' branch. I've been waiting for them
in order to push the NFS writeback improvements to Linus.
Would you be willing to either push the write_inode branch to Linus or
to Ack my doing so as part of the NFS push?
Cheers
Trond
next reply other threads:[~2010-03-05 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 15:26 Trond Myklebust [this message]
2010-03-05 15:48 ` Merge of the 'write_inode' branch from the VFS tree Al Viro
2010-03-05 17:40 ` [git pull] vfs part 3 (write_inode mess) Al Viro
2010-03-08 20:22 ` Steve Dickson
2010-03-09 8:52 ` Dave Chinner
2010-03-10 23:07 ` Trond Myklebust
2010-03-05 18:02 ` Merge of the 'write_inode' branch from the VFS tree Trond Myklebust
2010-03-05 18:29 ` Al Viro
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=1267802800.5174.6.camel@localhost.localdomain \
--to=trond.myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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