public inbox for linux-kernel@vger.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-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT-PULL] exofs: 2.6.35 merge window changes
Date: Sun, 23 May 2010 12:55:44 +0300	[thread overview]
Message-ID: <4BF8FBA0.3000801@panasas.com> (raw)

The following changes since "Linus 2.6.34" are available in the git
repository at:

  git://git.open-osd.org/linux-open-osd.git for-linus

Boaz Harrosh (1):
      exofs: Add default address_space_operations

Dan Carpenter (1):
      exofs: confusion between kmap() and kmap_atomic() api

 fs/exofs/dir.c   |    2 +-
 fs/exofs/inode.c |   30 ++++++++++++++++++++++++++++++
 2 files changed, 31 insertions(+), 1 deletions(-)

Very boring merge window for exofs. One cc:stable patch and another touch-base
maintenance patch. Most of the effort was spent on Testing and the surrounding
environment. The big enhancements are kept for future merges.

Thanks
Boaz

                 reply	other threads:[~2010-05-23  9:55 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=4BF8FBA0.3000801@panasas.com \
    --to=bharrosh@panasas.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox