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 Mailing List" <linux-kernel@vger.kernel.org>,
	"V9FS Developers" <v9fs-developer@lists.sourceforge.net>
Subject: [PULL] v9fs bug fixes and documentation updates for 2.6.26
Date: Wed, 14 May 2008 21:20:21 -0500	[thread overview]
Message-ID: <a4e6962a0805141920x7d96df33gb9c22a5777b1732c@mail.gmail.com> (raw)

Linus, please pull the following bug-fixes and documentation updates
from my kernel.org for-linus branch.

The following changes since commit dd286422fefdcff784e8d336deeb88ce817e14db:
  Linus Torvalds (1):
        Merge branch 'for-linus' of git://git.kernel.org/.../roland/infiniband

are available in the git repository at:

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

Eric Van Hensbergen (4):
      9p: Documentation updates
      9p: propagate parse_option changes to client and transports
      9p: make cryptic unknown error from server less scary
      9p: fix error path during early mount

Jim Meyering (1):
      fs/9p/v9fs.c (v9fs_parse_options): Handle kstrdup and
match_strdup failure. Now that this function can fail, return an int,
diagnose other option-parsing failures, and adjust the sole caller:
(v9fs_session_init): Handle kstrdup failure. Propagate any new
v9fs_parse_options failure "up".

Josef 'Jeff' Sipek (2):
      9p: use struct mutex instead of struct semaphore
      9p: Correct fidpool creation failure in p9_client_create

Markus Armbruster (1):
      add match_strlcpy() us it to make v9fs make uname and remotename
parsing more robust

Steven Rostedt (1):
      9p: fix flags length in net

 fs/9p/fid.h                |   15 +++
 fs/9p/v9fs.c               |   57 ++++++++---
 fs/9p/v9fs.h               |   85 +++++++++++-----
 fs/9p/vfs_addr.c           |    2 +-
 fs/9p/vfs_dir.c            |    2 +-
 fs/9p/vfs_file.c           |   11 +-
 fs/9p/vfs_inode.c          |   50 +++++++---
 fs/9p/vfs_super.c          |   35 +++----
 include/linux/parser.h     |    2 +-
 include/net/9p/9p.h        |  240 ++++++++++++++++++++++++++++++++++++++------
 include/net/9p/client.h    |   35 +++++++
 include/net/9p/transport.h |   44 ++++++++-
 lib/parser.c               |   32 ++++--
 net/9p/Kconfig             |   10 --
 net/9p/Makefile            |    3 -
 net/9p/client.c            |   32 +++++--
 net/9p/conv.c              |  128 +++++++++++++++++++++++-
 net/9p/error.c             |   15 ++-
 net/9p/fcprint.c           |    8 ++
 net/9p/mod.c               |    8 +-
 net/9p/trans_fd.c          |  204 +++++++++++++++++++++++++++++++-------
 net/9p/trans_virtio.c      |  175 ++++++++++++++++++++++++++++----
 net/9p/util.c              |   36 +++++--
 23 files changed, 1014 insertions(+), 215 deletions(-)

             reply	other threads:[~2008-05-15  2:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15  2:20 Eric Van Hensbergen [this message]
2008-05-15  2:40 ` Linus Torvalds
2008-05-15  2:43   ` Eric Van Hensbergen

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=a4e6962a0805141920x7d96df33gb9c22a5777b1732c@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®