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>
Subject: [GIT PULL] 9p changes for 2.6.32-rc1
Date: Wed, 23 Sep 2009 13:26:41 -0500	[thread overview]
Message-ID: <a4e6962a0909231126t734ee6e0i2be6d110e1d07758@mail.gmail.com> (raw)

Hi Linus,

The following changes since commit 7043078630bbc9eb908a56e08077c5abe7f2d311:
  David Howells (1):
        MN10300: Handle removal of struct uart_info

are available in the git repository at:

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

Abhishek Kulkarni (4):
      9p: Use the i_size_[read, write]() macros instead of using
inode->i_size directly.
      9p: Fix the incorrect update of inode size in v9fs_file_write()
      9p: Add fscache support to 9p
      9p: Update documentation to add fscache related bits

 Documentation/filesystems/9p.txt |   40 ++--
 fs/9p/Kconfig                    |    9 +
 fs/9p/Makefile                   |    3 +-
 fs/9p/cache.c                    |  474 ++++++++++++++++++++++++++++++++++++++
 fs/9p/cache.h                    |  176 ++++++++++++++
 fs/9p/v9fs.c                     |  196 ++++++++++++++--
 fs/9p/v9fs.h                     |   13 +-
 fs/9p/v9fs_vfs.h                 |    6 +
 fs/9p/vfs_addr.c                 |   88 +++++++-
 fs/9p/vfs_file.c                 |   25 ++-
 fs/9p/vfs_inode.c                |   61 +++++-
 fs/9p/vfs_super.c                |   16 +-
 include/net/9p/9p.h              |    3 +
 13 files changed, 1045 insertions(+), 65 deletions(-)
 create mode 100644 fs/9p/cache.c
 create mode 100644 fs/9p/cache.h

                 reply	other threads:[~2009-09-23 18:26 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=a4e6962a0909231126t734ee6e0i2be6d110e1d07758@mail.gmail.com \
    --to=ericvh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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®