From: Andrew Morton <akpm@linux-foundation.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: James.Bottomley@HansenPartnership.com, michaelc@cs.wisc.edu,
fujita.tomonori@lab.ntt.co.jp, jeff@garzik.org,
osd-dev@open-osd.org, linux-scsi@vger.kernel.org,
Sami.Iren@seagate.com, pw@padd.com, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: [PATCHSET 00/18] open-osd: OSD Initiator library for Linux
Date: Tue, 4 Nov 2008 11:19:23 -0800 [thread overview]
Message-ID: <20081104111923.bb19c238.akpm@linux-foundation.org> (raw)
In-Reply-To: <491073BB.4000900@panasas.com>
On Tue, 04 Nov 2008 18:09:31 +0200
Boaz Harrosh <bharrosh@panasas.com> wrote:
>
> Please consider for inclusion, an in-kernel OSD initiator
> library. Its main users are planned to be various OSD based file
> systems and the pNFS-Objects Layout Driver. (To be submitted soon)
>
> To try out and run the library please visit
> http://open-osd.org and follow the instructions there.
>
> The submitted patchset is also available via git at:
> git://git.open-osd.org/linux-open-osd.git osd
> http://git.open-osd.org/gitweb.cgi?p=linux-open-osd.git;a=shortlog;h=osd
>
> Or a compact out-of-tree repository that includes sources
> and some extras:
> git://git.open-osd.org/open-osd.git master
> http://git.open-osd.org/gitweb.cgi?p=open-osd.git;a=summary
>
> ...
>
> We would like this to sit in -mm tree for a while to make sure it is compilable
> on all platform.
The best way to do that is to include your git tree in linux-next. If
this code has a probably-will-be-merged-in-2.6.29 status then please
prepare a branch for Stephen to include in the linux-next lineup.
next parent reply other threads:[~2008-11-04 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48876009.8010701@panasas.com>
[not found] ` <491073BB.4000900@panasas.com>
2008-11-04 19:19 ` Andrew Morton [this message]
2008-11-05 13:56 ` [PATCHSET 00/18] open-osd: OSD Initiator library for Linux Boaz Harrosh
2008-11-09 14:58 ` Boaz Harrosh
2008-11-09 23:26 ` Stephen Rothwell
2008-11-10 12:52 ` Boaz Harrosh
2008-11-10 13:04 ` Stephen Rothwell
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=20081104111923.bb19c238.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Sami.Iren@seagate.com \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=osd-dev@open-osd.org \
--cc=pw@padd.com \
/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;
as well as URLs for NNTP newsgroup(s).