This looks like the path of least resistance. We can always change it in
the future if it's an issue. Cheers for handling this.
On Tue, Aug 27, 2013 at 9:18 AM, Jesse Gross wrote:
> I see what you mean about there being several implementations...
>
> The main thing that I was trying to get at w
I see what you mean about there being several implementations...
The main thing that I was trying to get at was whether we should add
some kind of dependency (through select/depends) or make the OVS SCTP
functionality dependent on a config option. We have the latter for
VXLAN and GRE support since
I must admit I'm not too familiar with the options here. Although I'm not
sure if it's directly related, it might not help that CRC32c has multiple
implementations.
There seems to be a discussion on this kind of issue below, where they
state the limitations of select and depend. In particular, the
On Fri, Aug 23, 2013 at 6:16 PM, kbuild test robot
wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/jesse/openvswitch.git
> master
> head: 810ddb4f57166b11e68291c33162007c394dbb7b
> commit: e1fa7d46ca3e698691cb1514bb4610d46e78bbd9 [9/10] openvswitch: Add SCTP
> support
> config:
