All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	open-osd <osd-dev@open-osd.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: [GIT PULL] exofs: changes for v2.6.39 merge window
Date: Wed, 23 Mar 2011 16:46:40 +0200	[thread overview]
Message-ID: <4D8A07D0.8070109@panasas.com> (raw)



Linus please pull the following few exofs changes since:
	commit [521cb40b] Linux 2.6.38

>From the git repository at:
  git://git.open-osd.org/linux-open-osd.git for-linus

The reason this is based on 2.6.38 is because all through the
rc window I was testing with external patches that only made
it in the final -rcs. So once 2.6.38 was released I have cut
a new tree, and re-run all the testes to make sure. It was since
sitting in linux-next.

This Merge window does not include the massive raid5 code, as it
is not reviewed and tested enough yet. I will postpone raid5 code
to the next Kernel.

Boaz Harrosh (5):
      exofs: Trivial: fix some indentation and debug prints
      exofs: Optimize read_4_write
      exofs: Override read-ahead to align on stripe_size
      exofs: Add option to mount by osdname
      exofs: Write sbi->s_nextid as part of the Create command
      exofs: deprecate the commands pending counter

Nick Piggin (1):
      exofs: simple fsync race fix

Tobias Klauser (1):
      exofs: Remove redundant unlikely()

 Documentation/filesystems/exofs.txt |   10 ++-
 fs/exofs/common.h                   |   18 +++-
 fs/exofs/dir.c                      |   33 ++++---
 fs/exofs/exofs.h                    |    6 +-
 fs/exofs/file.c                     |   16 +---
 fs/exofs/inode.c                    |   51 ++++++++--
 fs/exofs/super.c                    |  190 +++++++++++++++++++++++++++++++----
 7 files changed, 259 insertions(+), 65 deletions(-)

                 reply	other threads:[~2011-03-23 14:46 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=4D8A07D0.8070109@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=linux-fsdevel@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.