On Thu, Sep 17, 2015 at 1:22 PM, Pravin Shelar <pshe...@nicira.com> wrote: > On Thu, Sep 17, 2015 at 1:12 PM, Jesse Gross <je...@nicira.com> wrote: >> On Thu, Sep 17, 2015 at 11:49 AM, Pravin Shelar <pshe...@nicira.com> wrote: >>> On Wed, Sep 16, 2015 at 2:43 PM, Jesse Gross <je...@nicira.com> wrote: >>>> On Tue, Sep 15, 2015 at 11:09 AM, Pravin B Shelar <pshe...@nicira.com> >>>> wrote: >>>>> diff --git a/.travis.yml b/.travis.yml >>>>> index d14f786..f4b9188 100644 >>>>> --- a/.travis.yml >>>>> +++ b/.travis.yml >>>>> @@ -12,7 +12,8 @@ env: >>>>> - TESTSUITE=1 KERNEL=3.18.1 >>>>> - TESTSUITE=1 OPTS="--enable-shared" >>>>> - BUILD_ENV="-m32" OPTS="--disable-ssl" >>>>> - - KERNEL=4.0.2 >>>>> + - KERNEL=4.1.6 >>>>> + - KERNEL=4.0.9 >>>> >>>> Is there a reason to have both 4.0 and 4.1 tested? >>>> >>> right, I have removed it in next patch. >> >> But then the next patch adds 4.2 and keeps 4.1. I guess the larger >> point is, is there a reason to do test builds on each of these point >> releases or just do we only need the latest one? >> > I just wanted to keep it consistent with kernel versions listed on > kernel.org. Those kernel most likely change and therefore needs to be > compiled for.
OK, that's fine. I just wanted to make sure there was a reason. I think that means that all of my concerns were addressed without changes to this patch: Acked-by: Jesse Gross <je...@nicira.com> _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
