On Mon, 10 Sep 2012 15:09:22 -0500 Steve French <smfrench@xxxxxxxxx> wrote: > On Mon, Sep 10, 2012 at 7:58 AM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > > On Tue, 4 Sep 2012 12:06:25 -0500 > > Steve French <smfrench@xxxxxxxxx> wrote: > > > >> I plan to put these back in cifs-2.6.git for-next branch after > >> rescanning through them. for-next branch is resynced with linus's > >> tree as of yesterday. > > Sorry about that ... was out much of last three weeks (death in the family). > Ahh, sorry to hear that. Totally understood... > > We're at -rc5 now and Pavel's and my patches are *still* not in > > linux-next. Any ETA on getting that done? > > They are in for-next now (the first 47 patches, am still looking more > at the next 23). I also sent a merge request for the two patches for > 3.6 that had > been sitting for a week in the cifs-2.6.git tree (now in for-linus branch). > > > Steve, I'm still willing to maintain the linux-next branch if you don't > > have the time to deal with it. > > What would really help ... is a test automation process similar to > Samba (and Ganesha etc) for the kernel cifs.ko so we can make sure the > obvious (connectathon, fsx etc.) pass before we put in changes to > for-next. What does nfs kernel client do? I don't think there's any formal test infrastructure for the NFS client. Trond just tries to ensure that his for-next branch is updated in a timely fashion. I don't forsee us having such a thing without some paid lab monkeys to set it up and keep it running. -- Jeff Layton <jlayton@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
