On 7 May 2015 at 16:38, Jesse Gross <je...@nicira.com> wrote: > On Tue, May 5, 2015 at 2:01 PM, Joe Stringer <joestrin...@nicira.com> wrote: >> Signed-off-by: Joe Stringer <joestrin...@nicira.com> >> --- >> acinclude.m4 | 18 +++++++++--------- >> 1 file changed, 9 insertions(+), 9 deletions(-) > > Can you also update NEWS and the table in the FAQ? > >> diff --git a/acinclude.m4 b/acinclude.m4 >> index e9d0ed9..cd2301e 100644 >> --- a/acinclude.m4 >> +++ b/acinclude.m4 >> @@ -133,18 +133,18 @@ AC_DEFUN([OVS_CHECK_LINUX], [ >> fi >> AC_MSG_RESULT([$kversion]) >> >> - if test "$version" -ge 3; then >> - if test "$version" = 3 && test "$patchlevel" -le 19; then >> - : # Linux 3.x >> + if test "$version" -ge 4; then >> + if test "$version" != 4 || test "$patchlevel" -ge 1; then > > Is it possible to write the above test so that the number in the minor > version check is the highest supported? If I remember correctly, we > used to have something like this and people wouldn't notice that it > should be one higher than the actual number - i.e. when 4.1 is > supported the check wouldn't be updated because they already see a '4' > and a '1'.
Sure. I went back over and changed it to have the minimal set of changes , and to update those other files. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
