Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1642450
| From | Mauro Carvalho Chehab <mchehab@s-opensource.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST |
| Date | 2017-05-16 13:50 +0200 |
| Message-ID | <tHJ9g-56f-7@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <tHkDU-6ia-15@gated-at.bofh.it> <tHlqi-6SH-9@gated-at.bofh.it> <tHmFH-7ES-7@gated-at.bofh.it> <tHrYL-2FM-39@gated-at.bofh.it> <tHIGe-4Ub-7@gated-at.bofh.it> |
| Organization | Samsung |
Em Tue, 16 May 2017 13:16:56 +0200 Peter Zijlstra <peterz@infradead.org> escreveu: > On Mon, May 15, 2017 at 02:22:39PM -0300, Mauro Carvalho Chehab wrote: > > Yet, on the other hand, nobody wants lots of warnings/errors > > produced when building the Kernel or the documentation, as it can ride > > important things that would require fixes. > > So would that actually generate a warn/error? Or just generate weird > output? Both warn/error and weird output. From my side, the only reason for writing this patch is to fix the warnings that would otherwise be produced without it: ./kernel/futex.c:492: WARNING: Inline emphasis start-string without end-string. ./kernel/futex.c:1264: WARNING: Block quote ends without a blank line; unexpected unindent. ./kernel/futex.c:1721: WARNING: Block quote ends without a blank line; unexpected unindent. ./kernel/futex.c:2338: WARNING: Block quote ends without a blank line; unexpected unindent. ./kernel/futex.c:2426: WARNING: Block quote ends without a blank line; unexpected unindent. ./kernel/futex.c:2899: WARNING: Block quote ends without a blank line; unexpected unindent. ./kernel/futex.c:2972: WARNING: Block quote ends without a blank line; unexpected unindent. > > Because I'm perfectly fine with weird output. > > Our primary interface to the code is a text editor, and things should be > readable in that form. Anything that detracts from that is a fail. > > If people like to use web browsers (I don't) then I won't stop them, but > they have to realize they're the odd ducks out for viewing things > outside its native form. > > > diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c > > index 198527a62149..858a07590e39 100644 > > --- a/kernel/locking/mutex.c > > +++ b/kernel/locking/mutex.c > > @@ -227,9 +227,9 @@ static void __sched __mutex_lock_slowpath(struct mutex *lock); > > * (or statically defined) before it can be locked. memset()-ing > > * the mutex to 0 is not allowed. > > * > > - * ( The CONFIG_DEBUG_MUTEXES .config option turns on debugging > > - * checks that will enforce the restrictions and will also do > > - * deadlock debugging. ) > > + * (The CONFIG_DEBUG_MUTEXES .config option turns on debugging > > + * checks that will enforce the restrictions and will also do > > + * deadlock debugging) > > * > > * This function is similar to (but not equivalent to) down(). > > */ > > > > > > Thanks, Mauro
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2017-05-12 16:10 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Darren Hart <dvhart@infradead.org> - 2017-05-12 18:50 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2017-05-13 00:00 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Darren Hart <dvhart@infradead.org> - 2017-05-13 00:20 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2017-05-13 11:50 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Peter Zijlstra <peterz@infradead.org> - 2017-05-15 09:10 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2017-05-15 11:10 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Peter Zijlstra <peterz@infradead.org> - 2017-05-15 11:40 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Jani Nikula <jani.nikula@linux.intel.com> - 2017-05-15 12:30 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Peter Zijlstra <peterz@infradead.org> - 2017-05-15 13:50 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Jani Nikula <jani.nikula@linux.intel.com> - 2017-05-15 14:10 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Darren Hart <dvhart@infradead.org> - 2017-05-15 18:50 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2017-05-16 12:20 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2017-05-15 19:30 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Peter Zijlstra <peterz@infradead.org> - 2017-05-16 13:20 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Mauro Carvalho Chehab <mchehab@s-opensource.com> - 2017-05-16 13:50 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Darren Hart <dvhart@infradead.org> - 2017-05-13 00:20 +0200
Re: [PATCH 04/36] mutex, futex: adjust kernel-doc markups to generate ReST Peter Zijlstra <peterz@infradead.org> - 2017-05-13 00:20 +0200
csiph-web