linux-kernel.vger.kernel.org archive mirror
 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: fixes for -rc3
Date: Fri, 15 Apr 2011 17:02:16 -0500	[thread overview]
Message-ID: <BANLkTikrEVch9jmwpg4x3NGn03p1hHyC-w@mail.gmail.com> (raw)

Linus,
   Here's some fixes for the -rc stream, sorry these have been a bit
delayed due to a new baby killing my productivity and my normal sleep
patterns :)

The following changes since commit 5853b4f06f7b9b56f37f457d7923f7b96496074e:

  Merge branch 'for-linus' of git://git.kernel.dk/linux-2.6-block
(2011-04-15 08:01:13 -0700)

are available in the git repository at:

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

Aneesh Kumar K.V (5):
      fs/9p: Fix revalidate to return correct value
      fs/9p: Use write_inode for data sync on server
      9p: revert tsyncfs related changes
      fs/9p: Fix error reported by coccicheck
      9p: Fix sparse error

Harsh Prateek Bora (1):
      net/9p: nwname should be an unsigned int

 fs/9p/fid.c             |   15 +-------
 fs/9p/v9fs.h            |    1 -
 fs/9p/vfs_dentry.c      |    4 ++-
 fs/9p/vfs_inode_dotl.c  |    2 +-
 fs/9p/vfs_super.c       |   80 +++++++++++++++++++++++++++++++++--------------
 include/net/9p/9p.h     |    2 -
 include/net/9p/client.h |    5 +--
 net/9p/client.c         |   29 ++--------------
 net/9p/protocol.c       |    7 ++--
 net/9p/trans_common.c   |    2 +-
 net/9p/trans_virtio.c   |   15 ++++++--
 11 files changed, 84 insertions(+), 78 deletions(-)

                 reply	other threads:[~2011-04-15 22:02 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=BANLkTikrEVch9jmwpg4x3NGn03p1hHyC-w@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;
as well as URLs for NNTP newsgroup(s).