Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

2016-08-29 Thread Jacek Anaszewski
On 08/26/2016 05:58 PM, Rafał Miłecki wrote: On 25 August 2016 at 20:48, Jacek Anaszewski wrote: On 08/25/2016 04:30 PM, Alan Stern wrote: On Thu, 25 Aug 2016, Jacek Anaszewski wrote: I'd see it as follows: #cat available_ports #1-1 1-2 2-1 #echo "1-1" > new_port #cat observed_ports #1-1

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

2016-08-29 Thread Pavel Machek
Hi! > >2) Having "ports" subdir with RW files, one per each existing physical port > >In this situation we don't need "new_port" or "remove_port". If we > >want port to be observable we just do: > >echo 1 > 1-1 > >Implementing this solution needs reading more details from USB subsystem. > > The s

Re: [PATCH v3 0/3] USB Audio Gadget refactoring

2016-08-29 Thread Felipe Balbi
Hi, Ruslan Bilovol writes: > I came to this patch series when wanted to do two things: > - use UAC1 as virtual ALSA sound card on gadget side, >just like UAC2 is used so it's possible to do rate >resampling > - have both playback/capture support in UAC1 > > Since I wanted to have same

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

2016-08-29 Thread Rafał Miłecki
On 29 August 2016 at 10:05, Pavel Machek wrote: >> >2) Having "ports" subdir with RW files, one per each existing physical port >> >In this situation we don't need "new_port" or "remove_port". If we >> >want port to be observable we just do: >> >echo 1 > 1-1 >> >Implementing this solution needs re

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

2016-08-29 Thread Jacek Anaszewski
On 08/26/2016 09:50 PM, Pavel Machek wrote: On Thu 2016-08-25 20:48:04, Jacek Anaszewski wrote: On 08/25/2016 04:30 PM, Alan Stern wrote: On Thu, 25 Aug 2016, Jacek Anaszewski wrote: I'd see it as follows: #cat available_ports #1-1 1-2 2-1 #echo "1-1" > new_port #cat observed_ports #1-1 #

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

2016-08-29 Thread Pavel Machek
On Mon 2016-08-29 10:21:48, Rafał Miłecki wrote: > On 29 August 2016 at 10:05, Pavel Machek wrote: > >> >2) Having "ports" subdir with RW files, one per each existing physical > >> >port > >> >In this situation we don't need "new_port" or "remove_port". If we > >> >want port to be observable we j

Re: [PATCH 01/19] compat ABI: use non-compat openat and open_by_handle_at variants

2016-08-29 Thread Yury Norov
On Thu, Aug 25, 2016 at 05:52:11PM +0200, Arnd Bergmann wrote: > On Monday, August 15, 2016 5:30:28 PM CEST Yury Norov wrote: > > On Mon, Jun 27, 2016 at 09:47:38AM +0200, Andreas Schwab wrote: > > > Yury Norov writes: > > > > > > > The only difference is that non-compat version forces O_LARGEFIL

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

2016-08-29 Thread Rafał Miłecki
On 29 August 2016 at 10:41, Pavel Machek wrote: > On Mon 2016-08-29 10:21:48, Rafał Miłecki wrote: >> On 29 August 2016 at 10:05, Pavel Machek wrote: >> >> >2) Having "ports" subdir with RW files, one per each existing physical >> >> >port >> >> >In this situation we don't need "new_port" or "re

[PATCH] docs-rst: ignore arguments on macro definitions

2016-08-29 Thread Mauro Carvalho Chehab
A macro definition is mapped via .. c:function:: at the ReST markup when using the following kernel-doc tag: /** * DMX_FE_ENTRY - Casts elements in the list of registered * front-ends from the generic type struct list_head * to the typ

[PATCH v2] docs-rst: ignore arguments on macro definitions

2016-08-29 Thread Mauro Carvalho Chehab
A macro definition is mapped via .. c:function:: at the ReST markup when using the following kernel-doc tag: /** * DMX_FE_ENTRY - Casts elements in the list of registered * front-ends from the generic type struct list_head * to the typ

Re: [PATCH V2] Documentation: move oneshot trigger attributes documentation to ABI

2016-08-29 Thread Jacek Anaszewski
Hi Rafał, On 08/26/2016 04:19 PM, Rafał Miłecki wrote: From: Rafał Miłecki Documentation of sysfs interface should be in ABI in the first place. This moves relevant part of documentation and mentions where to look for it. Fix trivial typos whilst we are at it. Signed-off-by: Rafał Miłecki --

[PATCH v3] docs-rst: ignore arguments on macro definitions

2016-08-29 Thread Mauro Carvalho Chehab
A macro definition is mapped via .. c:function:: at the ReST markup when using the following kernel-doc tag: /** * DMX_FE_ENTRY - Casts elements in the list of registered * front-ends from the generic type struct list_head * to the typ

Re: [PATCH v3] docs-rst: ignore arguments on macro definitions

2016-08-29 Thread Markus Heiser
Am 29.08.2016 um 15:13 schrieb Mauro Carvalho Chehab : > A macro definition is mapped via .. c:function:: at the > ReST markup when using the following kernel-doc tag: > > /** >* DMX_FE_ENTRY - Casts elements in the list of registered >* front-ends from the ge

Re: [PACTH v2 0/3] Implement /proc//totmaps

2016-08-29 Thread Michal Hocko
[Sorry for a late reply, I was busy with other stuff] On Mon 22-08-16 15:44:53, Sonny Rao wrote: > On Mon, Aug 22, 2016 at 12:54 AM, Michal Hocko wrote: [...] > But what about the private_clean and private_dirty? Surely > those are more generally useful for calculating a lower bound on > process

Re: [PATCH v3] docs-rst: ignore arguments on macro definitions

2016-08-29 Thread Mauro Carvalho Chehab
Em Mon, 29 Aug 2016 16:12:39 +0200 Markus Heiser escreveu: > Am 29.08.2016 um 15:13 schrieb Mauro Carvalho Chehab > : > > > A macro definition is mapped via .. c:function:: at the > > ReST markup when using the following kernel-doc tag: > > > > /** > > * DMX_FE_ENTRY - Casts elements

Re: [PATCH v3] docs-rst: ignore arguments on macro definitions

2016-08-29 Thread Jani Nikula
On Mon, 29 Aug 2016, Mauro Carvalho Chehab wrote: > Em Mon, 29 Aug 2016 16:12:39 +0200 > Markus Heiser escreveu: > >> Am 29.08.2016 um 15:13 schrieb Mauro Carvalho Chehab >> : >> >> > A macro definition is mapped via .. c:function:: at the >> > ReST markup when using the following kernel-doc ta

Re: [PATCH v15 04/13] task_isolation: add initial support

2016-08-29 Thread Peter Zijlstra
On Tue, Aug 16, 2016 at 05:19:27PM -0400, Chris Metcalf wrote: > + /* > + * Request rescheduling unless we are in full dynticks mode. > + * We would eventually get pre-empted without this, and if > + * there's another task waiting, it would run; but by > + * explicitly reque

Re: [PATCH v15 04/13] task_isolation: add initial support

2016-08-29 Thread Peter Zijlstra
On Mon, Aug 29, 2016 at 12:40:32PM -0400, Chris Metcalf wrote: > On 8/29/2016 12:33 PM, Peter Zijlstra wrote: > >On Tue, Aug 16, 2016 at 05:19:27PM -0400, Chris Metcalf wrote: > >>+ /* > >>+* Request rescheduling unless we are in full dynticks mode. > >>+* We would eventually get pre-empt

Re: [PATCH v15 04/13] task_isolation: add initial support

2016-08-29 Thread Chris Metcalf
On 8/29/2016 12:33 PM, Peter Zijlstra wrote: On Tue, Aug 16, 2016 at 05:19:27PM -0400, Chris Metcalf wrote: + /* +* Request rescheduling unless we are in full dynticks mode. +* We would eventually get pre-empted without this, and if +* there's another task waiting,

Re: [PATCH v15 04/13] task_isolation: add initial support

2016-08-29 Thread Chris Metcalf
On 8/29/2016 12:48 PM, Peter Zijlstra wrote: On Mon, Aug 29, 2016 at 12:40:32PM -0400, Chris Metcalf wrote: On 8/29/2016 12:33 PM, Peter Zijlstra wrote: On Tue, Aug 16, 2016 at 05:19:27PM -0400, Chris Metcalf wrote: + /* +* Request rescheduling unless we are in full dynticks mode

Ping: [PATCH v15 00/13] support "task_isolation" mode

2016-08-29 Thread Chris Metcalf
On 8/16/2016 5:19 PM, Chris Metcalf wrote: Here is a respin of the task-isolation patch set. Again, I have been getting email asking me when and where this patch will be upstreamed so folks can start using it. I had been thinking the obvious path was via Frederic Weisbecker to Ingo as a NOHZ ki

Re: [PATCH v14 04/14] task_isolation: add initial support

2016-08-29 Thread Frederic Weisbecker
On Mon, Aug 15, 2016 at 10:59:55AM -0400, Chris Metcalf wrote: > On 8/11/2016 2:50 PM, Christoph Lameter wrote: > >On Thu, 11 Aug 2016, Frederic Weisbecker wrote: > > > >>Do we need to quiesce vmstat everytime before entering userspace? > >>I thought that vmstat only need to be offlined once and fo