Re: [PATCH] documentation: Fix two-CPU control-dependency example

2017-07-23 Thread Boqun Feng
On Sat, Jul 22, 2017 at 09:43:00PM -0700, Paul E. McKenney wrote: [...] > > Your priority seemed to be in reducing the chance of the "if" statement > > to be optimized away. So I suggested to use "extern" as a compromise. > Hi Akira, The problem is that, such a compromise doesn't help *develope

Re: [PATCH v2 0/8] Add a script to check for Sphinx install requirements

2017-07-23 Thread Jonathan Corbet
On Mon, 17 Jul 2017 18:46:34 -0300 Mauro Carvalho Chehab wrote: > Sphinx installation is not trivial, as not all versions are supported, > and it requires a lot of stuff for math, images and PDF/LaTeX output > to work. > > So, add a script that checks if everything is fine, providing > distro-sp

Re: [PATCH] docs: submitting-patches - change non-ascii character to ascii

2017-07-23 Thread Jonathan Corbet
On Fri, 21 Jul 2017 13:47:15 -0700 Frank Rowand wrote: > Ascii is a lowest common denominator. I can view and manipulate the file > with any common text editor and common text utilities (eg, cat, grep, etc) > on pretty much any Linux system that I walk up to. I don't need to go > to any effort

Re: [RFC PATCH 0/4] Documentation: generated module param documentation

2017-07-23 Thread Jonathan Corbet
On Wed, 19 Jul 2017 16:05:01 +0300 Jani Nikula wrote: > Hi Jon, all, here are some quick'n'dirty patches to semi-automatically > generate module param documentation from the source, via module build > and modinfo(8). No polish or proper design, just a hacked up > proof-of-concept to think about.

Re: [PATCH v2 0/8] Add a script to check for Sphinx install requirements

2017-07-23 Thread Mauro Carvalho Chehab
Em Sun, 23 Jul 2017 16:08:29 -0600 Jonathan Corbet escreveu: > On Mon, 17 Jul 2017 18:46:34 -0300 > Mauro Carvalho Chehab wrote: > > > Sphinx installation is not trivial, as not all versions are supported, > > and it requires a lot of stuff for math, images and PDF/LaTeX output > > to work. > >

Re: [PATCH] documentation: Fix two-CPU control-dependency example

2017-07-23 Thread Akira Yokosawa
On 2017/07/23 23:39:36 +0800, Boqun Feng wrote: > On Sat, Jul 22, 2017 at 09:43:00PM -0700, Paul E. McKenney wrote: > [...] >>> Your priority seemed to be in reducing the chance of the "if" statement >>> to be optimized away. So I suggested to use "extern" as a compromise. >> > > Hi Akira, > Hi

Re: [PATCH] documentation: Fix two-CPU control-dependency example

2017-07-23 Thread Paul E. McKenney
On Mon, Jul 24, 2017 at 09:04:57AM +0900, Akira Yokosawa wrote: > On 2017/07/23 23:39:36 +0800, Boqun Feng wrote: > > On Sat, Jul 22, 2017 at 09:43:00PM -0700, Paul E. McKenney wrote: > > [...] > >>> Your priority seemed to be in reducing the chance of the "if" statement > >>> to be optimized away.

Re: [PATCH] documentation: Fix two-CPU control-dependency example

2017-07-23 Thread Boqun Feng
On Mon, Jul 24, 2017 at 09:04:57AM +0900, Akira Yokosawa wrote: [...] > > > > ->8 > > Subject: [PATCH] kernel: Emphasize the return value of READ_ONCE() is > > honored > > > > READ_ONCE() is used around in kernel to provide a control dependency, > > and to make the control depend

Re: [PATCH 1/3] irq/irq_sim: add a simple interrupt simulator framework

2017-07-23 Thread Bartosz Golaszewski
2017-07-22 22:59 GMT+02:00 Jonathan Cameron : >> + >> +/** >> + * irq_sim_fire - Enqueue an interrupt. >> + * >> + * @sim:The interrupt simulator object. >> + * @offset: Offset of the simulated interrupt which should be fired. >> + */ >> +void irq_sim_fire(struct irq_sim *sim, unsigned