Closed davidker closed 8 years ago
The WARNING: char * array declaration might be better as static const
problems are now being handled via issue #11.
The error we have a pass from Dan C. I'm not sure if the pass is good enough to get out of staging, but it is a pass we can argue before we have to do it.
These should be fixed by my current patches on my upstream-next-selltc-20160325 branch: commit be8d5071523d84561a547aa789079b25d41a6ffb commit d849a9a923801b9632d380770294a7a800697a65 commit d1013a128d7863c2c6a833d40cd256a3250d0142 commit a79a3ebbb3a5976683214a62fef52f41de47cd27
Forgot to say... the previously-mentioned patches passed checkpatch and regression testing.
Greg accepted all of these except commit a79a3ebbb3a5976683214a62fef52f41de47cd27 (staging: unisys: visornic: convert BUG_ON to dev_err() message), to which he said:
Please return a real error number, don't make up error numbers like -1
I'll fix and re-submit a corrected patch.
Corrected patch is commit 09315e9f30936703611218013fc2e061de196cee.
This is compile-clean and checkpatch-clean.
Greg committed these to staging-next on 4/12:
Greg committed this to staging-next on 4/29: