The tool was specifically designed to fail in such a case, so there's nothing to *fix* there.
camera_list.csv exists to support the batch build processes. By definition, every port that can appear in a standard batch build will be listed. Some additional ports may be listed with SKIP_AUTOBUILD. These ports must be complete enough to run the standard -noskip operations like stubs rebuild.
You are free to use camera_list.csv for other purposes, but you should not assume it meets any criteria beyond what the build process requires.
There is no requirement that every sub-directory of platform have a matching camera_list entry.
although IMHO adding a LED test to trunk wasn't such a great idea.
I disagree. Having the initial digic 7 work preserved and publicly accessible is desirable, and this is the correct place to put it.