anchor.diff:  };
   ------------------
   
  -In 'platform/<platform>/test/foo/foo_main.c', register all the tests defined in
  -the 'foo' module, then mark a single specific test case as inactive:
  +In `platform/<platform>/test/foo/foo_main.c`, register all the tests defined in
  +the `foo` module, then mark a single specific test case as inactive:
   
   [source,c]
   ------------------
  
positive.code: This document is intended to guide a new ODP implementation developer.
  Further details about ODP may be found at http://opendataplane.org[ODP homepage]
  
  
  :numbered:
  == The include structure ==
  
  The implementers view of the include source tree allows the common interface
  definitions and documentation to be reused by all the platforms defined in the
  
negative.code: }
  ------------------
  
  So `foo_test_a` will be executed and `foo_test_b` is inactive.
  
  It's expected that early in the development cycle of a new implementation the
  inactive list will be quite long, but it should shrink over time as more parts
  of the API are implemented.
  
  ==== Conditional Tests
  
  Some tests may require specific conditions to make sense: for instance, on
  pktio, checking that sending a packet larger than the MTU is rejected only makes
  sense if packets can indeed, on that ODP implementation, exceed the MTU.
  A test can be marked conditional as follows:
  
  [source,c]
  ------------------
  