Re: [RFC] File naming conventions in /drivers/subsystem folders
Mitsis, Peter <Peter.Mitsis@...>
I am not clear what the added value of this proposed change brings. I get that there is the redundancy in the full path name, but what is the problem of redundancy in this case? The big advantage of the redundancy in this case is that it provides contextual information for when the preceding path is not available. Consider the following two case ...toggle quoted messageShow quoted text
1. If editing a file, the preceding path might not be shown in the title bar or tab. This may make the editing of the files more error prone as it becomes easier to mix up files "adc/dw.c" and "spi/dw.c".
2. A similar argument may apply to a printed file. The otherwise easily identified contextual information may be lost if only the filename is shown on the header/footer of the page.
What about use of the __FILE__ macro? Do we have cases where only the filename would be displayed? If so, then this too increases the likelihood of misidentifying a file.