On Aug 8, 2012, at 1:34 PM, Jesse Gross wrote: > On Wed, Aug 8, 2012 at 11:13 AM, Kyle Mestery (kmestery) > <kmest...@cisco.com> wrote: >> On Aug 8, 2012, at 1:08 PM, Jesse Gross wrote: >>> On Tue, Aug 7, 2012 at 3:48 PM, Kyle Mestery <kmest...@cisco.com> wrote: >>>> Signed-off-by: Kyle Mestery <kmest...@cisco.com> >>>> --- >>>> datapath/datapath.c | 4 ++-- >>>> 1 file changed, 2 insertions(+), 2 deletions(-) >>> >>> Applied, thanks Kyle. >> >> Thanks Jesse. Fedora rolled up to this version, so to keep using OVS, this >> was >> necessary. >> >> Just curious, does this check basically ensure that someone at least runs >> OVS with >> future versions of the kernel before committing it into the OVS tree? Is it >> preventing people from shooting themselves in the foot in case an API changes >> upstream? > > The latter. In the best case, when something changes upstream users > get a bunch of compiler errors and complain that OVS doesn't work. In > the worst case, the API that OVS uses doesn't change but the meaning > does and things compile but crash or otherwise misbehave. In this > case nothing needed to change but that's pretty rare.
Thanks for the explanation Jesse, this makes sense to me. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
