From: Jeff Garzik <jeff@garzik.org>
To: Boaz Harrosh <bharrosh@panasas.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
open-osd mailing-list <osd-dev@open-osd.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [GIT PULL resend] exofs/osd tree for 2.6.31-rc2
Date: Fri, 10 Jul 2009 18:21:58 -0400 [thread overview]
Message-ID: <4A57BF06.1070601@garzik.org> (raw)
In-Reply-To: <4A54666C.5010407@panasas.com>
Boaz Harrosh wrote:
> 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
Ping... is there a problem with this pull?
Maybe Linus is expecting exofs stuff through James?
Jeff
prev parent reply other threads:[~2009-07-10 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 9:27 [GIT PULL resend] exofs/osd tree for 2.6.31-rc2 Boaz Harrosh
2009-07-10 22:21 ` Jeff Garzik [this message]
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=4A57BF06.1070601@garzik.org \
--to=jeff@garzik.org \
--cc=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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.