On 11/10/2016 10:14 AM, Lorenzo Colitti wrote: > So you'd split SRH functionality in three parts? Core (default on), > lwtunnel (default off) and inline? > > It seems to me that once you've done the work to enable the core code > to work when CONFIG_LWTUNNEL is off, you can just enable/disable the > LWT part of SRH depending on whether CONFIG_LWTUNNEL is compiled in or > not. That might save you a config option.
That would be easier indeed, but then this behavior should be documented somewhere: how the user would know that it has to enable CONFIG_LWTUNNEL ? David
signature.asc
Description: OpenPGP digital signature
