On Tue, Oct 13, 2020 at 02:11:16PM +0100, Matthew Wilcox wrote: > On Tue, Oct 13, 2020 at 02:52:06PM +0200, Peter Zijlstra wrote: > > On Tue, Oct 13, 2020 at 02:14:31PM +0200, Mauro Carvalho Chehab wrote: > > > + ===== =================================================== > > > + ``.`` acquired while irqs disabled and not in irq context > > > + ``-`` acquired in irq context > > > + ``+`` acquired with irqs enabled > > > + ``?`` acquired in irq context with irqs enabled. > > > + ===== =================================================== > > > > NAK! > > You're seriously suggesting that: > > - === =================================================== > - '.' acquired while irqs disabled and not in irq context > - '-' acquired in irq context > - '+' acquired with irqs enabled > - '?' acquired in irq context with irqs enabled. > - === =================================================== > + ===== =================================================== > + ``.`` acquired while irqs disabled and not in irq context > + ``-`` acquired in irq context > + ``+`` acquired with irqs enabled > + ``?`` acquired in irq context with irqs enabled. > + ===== =================================================== > > this change makes the lockdep docs less readable? Definitely makes it harder to read for me. My C trained eyes go WTF at seeing it, which breaks the flow. ',' is a regular single character constant, '','' a syntax error. > It's not the markup that makes the lockdep documentation hard to > understand. I'm not sure what you're alluding to, the subject just isn't easy to begin with. Over all I'm tempted to just convert the whole thing to .txt and avoid all the RST shit entirely.
