Thread (34 messages) 34 messages, 6 authors, 2019-11-21

Re: [PATCH v2 2/8] cdrom: factor out common open_for_* code

From: Christoph Hellwig <hch@infradead.org>
Date: 2019-10-25 02:38:36
Also in: linux-fsdevel, linux-scsi, lkml

On Thu, Oct 24, 2019 at 06:23:14AM -0700, Matthew Wilcox wrote:
On Wed, Oct 23, 2019 at 07:19:58PM -0700, Christoph Hellwig wrote:
quoted
quoted
 static
-int open_for_data(struct cdrom_device_info *cdi)
+int open_for_common(struct cdrom_device_info *cdi, tracktype *tracks)
Please fix the coding style.  static never should be on a line of its
own..
It's OK to have the static on a line by itself; it's having 'static int'
on a line by itself that Linus gets unhappy about because he can't use
grep to see the return type.
Sorry, but independent of any preference just looking at the codebases
proves you wrong.  All on one line is the most common style, but not
by much, followed by static + type.  Just static is just in a few crazy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help