On 2013-04-27, at 10:12 AM, Peng Tao wrote: > On Sat, Apr 27, 2013 at 11:56 PM, Andi Kleen <ak@xxxxxxxxxxxxxxx> wrote: >>> The rules for staging are: >>> - it has to build >>> - it has to be self-contained in drivers/staging/YOUR_NAME/ >>> - it has to have a correct license (i.e. GPLv2 compatible). >>> - it has to have a TODO file listing what needs to be done in >>> order to get it out of staging. >>> that's it. >> >> Traditionally Lustre needed some patches in fs/* >> I don't know if that's still the case. >> >> But if yes you would likely need to get those in first separately. > > Those are only needed for Lustre server now. For client, there is no > need to patch other parts out side of fs/lustre and net/lnet. > > But thanks for mentioning. Tao, thanks for starting to look into this. Does it really make sense to stage a filesystem under drivers/*? IMHO it makes a lot more sense to put the components into the location where they would live in the upstream kernel tree (i.e. fs/lustre and net/lnet). Also a question for you - what version of the Lustre client are you intending to submit to the staging tree? We are very close to the 2.4.0 release, so it definitely makes sense to start with that one. There is also the question of how you will keep the staging client in-sync with the development done in the upstream Lustre repo? There has definitely been a lot of work done to clean up the Lustre code, but there is still a considerable amount of work left to be done. In particular, the CLIO layer needs a bunch of cleanup to become more efficient and understandable. Cheers, Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
