On Tue, May 23, 2017 at 10:11:59AM +0200, hch wrote: > On Mon, May 15, 2017 at 05:44:50PM +0200, hch wrote: > > On Mon, May 15, 2017 at 11:21:34AM -0400, bfields@xxxxxxxxxxxx wrote: > > > On Sat, May 13, 2017 at 04:10:21PM +0000, Trond Myklebust wrote: > > > > Right, so the alternative is that either Bruce or Anna merges the full > > > > set, and then both pull that common base into their linux-next branches > > > > on linux-nfs.org, and we then ask everyone to develop their 4.13 > > > > patches against those branches. That would work too... > > > > > > I like that. Christoph, could you just give us a 12-rc1-based branch to > > > base our 4.13 work on? > > > > git://git.infradead.org/users/hch/vfs.git nfs-ops > > > > Gitweb: > > > > http://git.infradead.org/users/hch/vfs.git/shortlog/refs/heads/nfs-ops > > Any progress on picking this up somewhere? Unfortunately I can't get anything through testing. It's not your patches, it's something in -rc1. My server VM stops responding to any network traffic randomly in the middle of a run. If I log in from a serial console, I see the interface is up and everything looks OK. I haven't had the chance to do much more, and I'm not sure where to start.... I started a git-bisect attempt, but there are several unrelated problems, and I'm not sure this one is 100% reproduceable. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
