anchor.diff:  
   === Platform specific
   
  -These tests are located under `platform/<platform>/test`. There is one such
  -area for each platform implementing ODP.  This location will be referred as
  +These tests are located under `platform/<platform_name>/`. There is one such
  +area for each platform implementing ODP. This location will be referred as
   <PLATFORM_SPECIFIC> in the rest of this document.
   
   ==== The normal case
  
positive.code: some functionality: For instance, testing `odp_cpumask_*` could involve checking
  the underlying system CPU mask. On linux, such a test would require using the
  CPU_ISSET macro, which is linux specific. Such a test would be written in
  `<PLATFORM_SPECIFIC>/cpumask/...` The contents of this directory would be very
  similar to the contents of the platform agnostic side cpu_mask tests
  (including a `Makefile.am`), but platform specific test would be written there.
  `<PLATFORM_SPECIFIC>/Makefile.am` would then trigger the building of the
  platform specific tests (by listing their module name in `SUBDIRS` and therefore
  calling the appropriate `Makefile.am`) and then it would call both the platform
  agnostic executable(s) and the platform specific test executable.
  
  ==== Marking tests as inactive
  
  The general policy is that a full run of the validation suite (a `make check`)
  must pass at all times. However a particular platform may have one or more test
  
negative.code: as inactive. Inactive tests are registered with the test framework but aren't
  executed and will be recorded as inactive in test reports.
  
  In `test/common_plat/validation/api/foo/foo.c`, define all
  validation tests for the 'foo' module:
  
  [source,c]
  ------------------
  