Dear Peter Tyser,
In message 1247157371.905.16.camel@localhost.localdomain you wrote:
Please don't do this. I would like to have api_examples stay clear from the API proper and such organization was introduced on purpose. While the core API code is integral part of U-Boot code image, the example/demo/other app is physically separate tangible entity. I think it seems proper that directories' layout reflects this. What we could do is provide a top level directory grouping all items non-integral wrt U-Boot itself (examples, api_examples) and put them there.
I don't really follow... The api_example/ directory is an example of how to use the functionality provided by the code in the api/ directory, right? If so, they are very closely related and I'd argue that the api_example/ directory should be moved into api/ since conceptually it makes more sense as well as cleans up the directory structure.
If a directory gets created, I'd prefer to see this under
examples/api/
then, assuming that more types of example code might get added over time, and I think it would be nice to have these together.
Best regards,
Wolfgang Denk