From: Eric Van Hensbergen <ericvh@gmail.com>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
V9FS Developers <v9fs-developer@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] 9p file system bug fixes
Date: Tue, 26 Jan 2010 16:44:59 -0600 [thread overview]
Message-ID: <a4e6962a1001261444l1235a15dxada6964151ffe119@mail.gmail.com> (raw)
Linus,
Please pull a couple of bug fixes for the 9P filesystem for 2.6.33-rc
The following changes since commit 7284ce6c9f6153d1777df5f310c959724d1bd446:
Linus Torvalds (1):
Linux 2.6.33-rc4
are available in the git repository at:
ssh://master.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git for-linus
Eric Van Hensbergen (3):
net/9p: fix virtio transport to correctly update status on connect
net/9p: fail when user specifies a transport which we can't find
net/9p: fix statsize inside twstat
net/9p/client.c | 13 +++++++++++--
net/9p/trans_virtio.c | 1 +
2 files changed, 12 insertions(+), 2 deletions(-)
Thanks,
-eric
reply other threads:[~2010-01-26 22:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a4e6962a1001261444l1235a15dxada6964151ffe119@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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).