Re: [PATCH] samples: move blackfin gptimers-example from Documentation

On 09/23/2016 05:45 PM, Shuah Khan wrote: > Move blackfin gptimers-example to samples and remove the Documentation > Makefile. Update samples Kconfig and Makefile to build gptimers-example. > > Signed-off-by: Shuah Khan This patch isn't complete. CONFIG_BUILD_DOCSRC=1

Re: [RFC] fs: add userspace critical mounts event support

On 03/09/2016 11:10, Dmitry Torokhov wrote: > I was thinking if we kernel could post > "conditions" (maybe simple stings) that it waits for, and userspace > could unlock these "conditions". One of them might be "firmware > available". On idea offered by Josh Triplett that seems to overlap with

[PATCH -tip] locking/rtmutex: Reduce top-waiter blocking on a lock

By applying well known spin-on-lock-owner techniques, we can avoid the blocking overhead during the process of when the task is trying to take the rtmutex. The idea is that as long as the owner is running, there is a fair chance it'll release the lock soon, and thus a task trying to acquire the

Re: [PATCH] docs-rst: add inter-document cross references

Hi Jon, Em Wed, 21 Sep 2016 15:44:05 -0600 Jonathan Corbet escreveu: > ...and now I'm thinking that's maybe about enough in docs for 4.9...:) I finished handling the plain text files that, IMHO, should be on either user of development process books. As you're feeling that

Re: [RFC PATCH v3] docs-rst: user: add MAINTAINERS

Em Fri, 23 Sep 2016 09:26:34 -0700 Joe Perches escreveu: > On Fri, 2016-09-23 at 12:07 -0300, Mauro Carvalho Chehab wrote: > > So, let's use an unusual approach: manually convert the > > text at the MAINTAINERS file head, adding it at a new > >

Re: [RFC PATCH v3] docs-rst: user: add MAINTAINERS

Am 23.09.2016 um 17:35 schrieb Mauro Carvalho Chehab : > Em Fri, 23 Sep 2016 09:15:01 -0600 > Jonathan Corbet escreveu: >> I'm not sure I see the value of including it in >> the docs? What am I missing here? > > It is part of the REPORTING-BUGS

Re: [RFC PATCH v3] docs-rst: user: add MAINTAINERS

On Fri, 2016-09-23 at 12:07 -0300, Mauro Carvalho Chehab wrote: > So, let's use an unusual approach: manually convert the > text at the MAINTAINERS file head, adding it at a new > Documentation/user/MAINTAINERS.rst, and include, as a code > block, the rest of MAINTAINERS contents, with only the >

Re: [RFC PATCH v3] docs-rst: user: add MAINTAINERS

Em Fri, 23 Sep 2016 09:15:01 -0600 Jonathan Corbet escreveu: > On Fri, 23 Sep 2016 12:07:33 -0300 > Mauro Carvalho Chehab wrote: > > > including MAINTAINERS using ReST is tricky, because all > > maintainer's entries are like: > > So I'm generally in

[RFC PATCH v3] docs-rst: user: add MAINTAINERS

including MAINTAINERS using ReST is tricky, because all maintainer's entries are like: FOO SUBSYSTEM: M: My Name L: mailing@list S: Maintained F: foo/bar On ReST, this would be displayed on a single line. Using alias, like |M|, |L|, ... won't solve, as an alias in Sphinx doesn't accept

Re: [RFC PATCH v3] docs-rst: user: add MAINTAINERS

On Fri, 23 Sep 2016 12:07:33 -0300 Mauro Carvalho Chehab wrote: > including MAINTAINERS using ReST is tricky, because all > maintainer's entries are like: So I'm generally in favor of moving things over to RST, but I have to ask: what's the payoff for doing that with

[RFC PATCHv2] docs-rst: user: add MAINTAINERS

including MAINTAINERS using ReST is tricky, because all maintainer's entries are like: Thanks, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[RFC PATCH] docs-rst: user: add MAINTAINERS

including MAINTAINERS using ReST is tricky, because all maintainer's entries are like: FOO SUBSYSTEM: M: My Name L: mailing@list S: Maintained F: foo/bar On ReST, this would be displayed on a single line. Using alias, like |M|, |L|, ... won't solve, as an alias in Sphinx doesn't accept

Re: [RFC PATCH 08/11] pci: controller: dra7xx: Add EP mode support

On Wed, Sep 14, 2016 at 10:42:04AM +0530, Kishon Vijay Abraham I wrote: > The PCIe controller integrated in dra7xx SoCs is capable of operating > in endpoint mode. Add support for dra7xx SoCs to operate in endpoint > mode. > > Signed-off-by: Kishon Vijay Abraham I > --- >

Re: [RFC PATCH 07/11] pci: controller: designware: Add EP mode support

On Wed, Sep 14, 2016 at 10:42:03AM +0530, Kishon Vijay Abraham I wrote: > Add endpoint mode support to designware driver. This uses the > EP Core layer introduced recently to add endpoint mode support. > *Any* function driver can now use this designware device > to achieve the EP functionality. >

Re: [PATCH v2 0/3] Move runnable tools from Documentation to tools

On 09/22/2016 08:57 AM, Jonathan Corbet wrote: > On Wed, 21 Sep 2016 18:51:10 -0600 > Shuah Khan wrote: > >> Move runnable tools from Documentation to tools. I moved just the >> tools code, and left documentation files as is. >> >> Based on the v1 series feedback, This

Re: [RFC PATCH v2 3/5] futex: Throughput-optimized (TO) futexes

On Thu, 22 Sep 2016, Waiman Long wrote: > On 09/22/2016 04:38 PM, Thomas Gleixner wrote: > > > wait-wake futex PI futexTO futex > > > --- > > > max time3.49s50.91s 2.65s > > >

Re: [RFC PATCH 3/4] futex: Throughput-optimized (TO) futexes

On Thu, 22 Sep 2016, Waiman Long wrote: > On 09/22/2016 09:32 AM, Thomas Gleixner wrote: > > > + WARN_ON(!pi_state->owner); > > > + if (pi_state->owner) > > > + wake_up_process(pi_state->owner); > > And what handles or sanity checks the