> On Sep 11, 2015, at 5:02 PM, Joe Stringer <joestrin...@nicira.com> wrote: > > On 11 September 2015 at 16:37, Jarno Rajahalme <jrajaha...@nicira.com> wrote: >> Here is an provisional ACK, I trust you to address the comments to my >> satisfaction :-) >> >> Acked-by: Jarno Rajahalme <jrajaha...@nicira.com> >> >> Jarno > > Thanks, but I may yet send a round 2; there's a lot of scattered > changes, so I wouldn't mind getting
> some extra viewing on the patches. > Exactly what I was trying to avoid ;-) Jarno > <snip> > >>> Hmm, I don't have a good solution for this. Personally I always push >>> code to a remote test VM that I use specifically for the purpose of >>> running these tests, so any configuration I might have in my local >>> desktop environment wouldn't cause issues such as this. (This is >>> equivalent to how the Vagrant tests run) >> >> Maybe a comment in some doc describing how to run check-kernel? > > I could've sworn that we had some description like this, but it seems > not. It's all hidden under the Vagrant how-to in INSTALL.md. Sounds > like a good idea. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
