From: Boaz Harrosh <bharrosh@panasas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>
Subject: [GIT PULL] exofs: few changes for the 2.6.37 merge window
Date: Mon, 25 Oct 2010 19:05:08 +0200 [thread overview]
Message-ID: <4CC5B8C4.9060306@panasas.com> (raw)
Linus please pull the following changes since commit cd07202c
Linux 2.6.36-rc8 (2010-10-14 16:26:43 -0700)
>From the git repository at:
git://git.open-osd.org/linux-open-osd.git for-linus
Just a few fixes and cleanups that have accumulated. Nothing
really exiting expect one patch that is important for Nick's
scalability work.
Boaz Harrosh (3):
exofs: Cleaup read path in regard with read_for_write
exofs: Set i_mapping->backing_dev_info anyway
exofs: Remove inode->i_count manipulation in exofs_new_inode
Joe Perches (1):
fs/exofs: typo fix of faild to failed
fs/exofs/dir.c | 4 +-
fs/exofs/inode.c | 78 ++++++++++++++++++++++-------------------------------
fs/exofs/ios.c | 10 +++---
3 files changed, 39 insertions(+), 53 deletions(-)
Thanks
Boaz
reply other threads:[~2010-10-25 17:05 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=4CC5B8C4.9060306@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osd-dev@open-osd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.