Andrew Morton wrote: > On Tue, 04 Nov 2008 18:09:31 +0200 > Boaz Harrosh <bharrosh@xxxxxxxxxxx> 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. > Thanks Andrew I was thinking this code would eventually go into Linux-next threw James tree. But thought if there was a way for some exposure, so to give James some confidence in the code before he commits to it. But this way it could be perfect, thanks. Stephen Hi I have just that branch ready it is: git://git.open-osd.org/linux-open-osd.git osd Note the "osd" branch. Do I need to call it something special like "linux-next"? (Give me 24 hours to fix all current comments) Also one more question. This tree is based on latest scsi-misc-2.6.git, Because it is destined to go threw James tree at the end. Do I need to prepare a special tree based on Linus-latest? Thanks in advance Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
