From: Boaz Harrosh <bharrosh@panasas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Jeff Garzik <jeff@garzik.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
open-osd mailing-list <osd-dev@open-osd.org>
Subject: [GIT PULL resend] exofs/osd tree for 2.6.31-rc2
Date: Wed, 08 Jul 2009 12:27:08 +0300 [thread overview]
Message-ID: <4A54666C.5010407@panasas.com> (raw)
Linus
Please pull the following exofs/OSD changes from the git repository at:
git://git.open-osd.org/linux-open-osd.git for-linus
These are a few fixes/cleanups and mainly a new block-device driver
from Jeff Garzik, that can export an OSD object to block-based users
like filesystems.
Since they are all small bug fixes, the copyrights adjustment should be looked
at as a bug in the file ownership. (the original removal request came from IBM.)
And one new driver. It might be said that we do not violate -rc rules with this.
Boaz Harrosh (5):
exofs: Fix bio leak in error handling path (sync read)
exofs: Remove IBM copyrights
exofs: Avoid using file_fsync()
MAINTAINERS: Add osd maintained files (F:)
osdblk: Adjust queue limits to lower device's limits
Jeff Garzik (1):
osdblk: a Linux block device for OSD objects
MAINTAINERS | 5 +-
drivers/block/Kconfig | 16 ++
drivers/block/Makefile | 1 +
drivers/block/osdblk.c | 670 ++++++++++++++++++++++++++++++++++++++++++++++++
fs/exofs/common.h | 4 +-
fs/exofs/dir.c | 4 +-
fs/exofs/exofs.h | 7 +-
fs/exofs/file.c | 21 +-
fs/exofs/inode.c | 7 +-
fs/exofs/namei.c | 4 +-
fs/exofs/osd.c | 4 +-
fs/exofs/super.c | 6 +-
fs/exofs/symlink.c | 4 +-
13 files changed, 719 insertions(+), 34 deletions(-)
create mode 100644 drivers/block/osdblk.c
[These patches can be viewed on the web here:
http://git.open-osd.org/gitweb.cgi?p=linux-open-osd.git;a=shortlog;h=refs/heads/for-linus
]
Thanks
Boaz
next reply other threads:[~2009-07-08 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 9:27 Boaz Harrosh [this message]
2009-07-10 22:21 ` [GIT PULL resend] exofs/osd tree for 2.6.31-rc2 Jeff Garzik
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=4A54666C.5010407@panasas.com \
--to=bharrosh@panasas.com \
--cc=jeff@garzik.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox