mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 file system bug fixes for 2.6.34-rc3
Date: Mon, 5 Apr 2010 15:40:12 -0500	[thread overview]
Message-ID: <i2la4e6962a1004051340n741c2594s5765dfdc85414e7b@mail.gmail.com> (raw)

Linus,

The following changes since commit db217dece3003df0841bacf9556b5c06aa097dae:
  Linus Torvalds (1):
        Merge git://git.kernel.org/.../davem/sparc-2.6

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git for-linus

Aneesh Kumar K.V (3):
      fs/9p: Clunk the fid resulting from partial walk of the name
      9p: drop nlink remove
      9p: Make sure we are able to clunk the cached fid on umount

Dan Carpenter (2):
      9p: return on mutex_lock_interruptible()
      9p: saving negative to unsigned char

Sripathi Kodi (3):
      9p: Fix setting of protocol flags in v9fs_session_info structure.
      9p: documentation update
      9p: Creating files with names too long should fail with ENAMETOOLONG.

 Documentation/filesystems/9p.txt |   18 ++++++++++++++++--
 fs/9p/fid.c                      |   12 ++++++++++--
 fs/9p/v9fs.c                     |   21 ++++++++++++++++++---
 fs/9p/v9fs.h                     |    1 +
 fs/9p/vfs_dir.c                  |    2 ++
 fs/9p/vfs_inode.c                |    9 ++++++++-
 fs/9p/vfs_super.c                |    3 ++-
 include/net/9p/client.h          |    2 ++
 net/9p/client.c                  |   23 +++++++++++++++++++----
 9 files changed, 78 insertions(+), 13 deletions(-)

    thanks,

           -eric

                 reply	other threads:[~2010-04-05 20:40 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=i2la4e6962a1004051340n741c2594s5765dfdc85414e7b@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®