From: Eric Van Hensbergen <ericvh@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
V9FS Developers <v9fs-developer@lists.sourceforge.net>
Subject: [GIT PULL] 9p bug fixes for 2.6.31-rc7
Date: Thu, 27 Aug 2009 08:47:04 -0500 [thread overview]
Message-ID: <a4e6962a0908270647r182191ftf833590924f066b8@mail.gmail.com> (raw)
Linus, please pull this set of bug fixes and minor documentation
revisions. Thanks.
The following changes since commit 3edf2fb9d80a46d6c32ba12547a42419845b4b76:
Linus Torvalds (1):
Merge branch 'for-linus' of git://git.kernel.org/.../jbarnes/pci-2.6
are available in the git repository at:
ssh://master.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git for-linus
Abhishek Kulkarni (10):
9p: Check for error in return value of v9fs_fid_add
9p: Fix possible inode leak in v9fs_get_inode.
9p: minor comment fixes
9p: Fix possible memleak in v9fs_inode_from fid.
9p: Fix v9fs show_options
9p: Fix possible regressions when ->get_sb fails.
9p: Remove redundant inode uid/gid assignment
9p: Add missing cast for the error return value in v9fs_get_inode
net/9p: insulate the client against an invalid error code sent
by a 9p server
9p: remove unnecessary v9fses->options which duplicates the mount string
Eric Van Hensbergen (1):
9p: update documentation pointers
Documentation/filesystems/9p.txt | 3 +
fs/9p/v9fs.c | 21 ++-----
fs/9p/v9fs.h | 1 -
fs/9p/vfs_inode.c | 126 +++++++++++++++++++------------------
fs/9p/vfs_super.c | 39 ++++--------
net/9p/client.c | 21 +++----
net/9p/error.c | 2 +-
net/9p/trans_fd.c | 8 +-
net/9p/trans_rdma.c | 9 ++-
net/9p/trans_virtio.c | 11 +--
10 files changed, 107 insertions(+), 134 deletions(-)
reply other threads:[~2009-08-27 13:47 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=a4e6962a0908270647r182191ftf833590924f066b8@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®