Re: [v8 0/4] cgroup-aware OOM killer

On Tue, Sep 19, 2017 at 01:54:48PM -0700, David Rientjes wrote: > On Fri, 15 Sep 2017, Roman Gushchin wrote: > > > > > > But then you just enforce a structural restriction on your > > > > > configuration > > > > > because > > > > > root > > > > > / \ > > > > >AD > > >

Re: [v8 0/4] cgroup-aware OOM killer

On Mon, Sep 18, 2017 at 08:14:05AM +0200, Michal Hocko wrote: > On Fri 15-09-17 08:23:01, Roman Gushchin wrote: > > On Fri, Sep 15, 2017 at 12:58:26PM +0200, Michal Hocko wrote: > > > On Thu 14-09-17 09:05:48, Roman Gushchin wrote: > > > > On Thu, Sep 14, 2017 at 03:40:14PM +0200, Michal Hocko

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

On 09/20/2017 01:29 PM, Pavel Machek wrote: > I'd leave the decision to the user. We could add a note to the > Documentation/leds/ledtrig-transient.txt that force feedback interface > should be preferable choice for driving vibrate devices. > However only if following conditions

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

On 09/19/2017 11:07 PM, Dmitry Torokhov wrote: > On Tue, Sep 19, 2017 at 1:45 PM, Jacek Anaszewski > wrote: >> On 09/19/2017 12:29 AM, Dmitry Torokhov wrote: >>> On Mon, Sep 18, 2017 at 1:50 PM, Jacek Anaszewski >>> wrote: Hi,

[PATCH 21/25] scripts: kernel-doc: fix nexted handling

At DVB, we have, at some structs, things like (see struct dvb_demux_feed, at dvb_demux.h): union { struct dmx_ts_feed ts; struct dmx_section_feed sec; } feed; union { dmx_ts_cb ts; dmx_section_cb sec;

[PATCH 00/25] DVB cleanups and documentation improvements

This patch series comes after a previous patchset with DVB fixes. both series are there at: https://git.linuxtv.org/mchehab/experimental.git/log/?h=dvb-fixes-v3 It is mainly focused on improving the DVB kAPI documentation, making it (finally!) in sync with the current implementation. It also

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

Hi, On 09/20/2017 01:15 PM, Pavel Machek wrote: > On Mon 2017-09-18 22:43:40, Jacek Anaszewski wrote: >> Hi, >> >> On 09/17/2017 07:50 PM, Pavel Machek wrote: >>> Hi! >>> >> Do you think such an improvement could be harmful in some way, >> even if it was made optional? > > Of

[PATCH] scripts: kernel-doc: fix nexted handling

At DVB, we have, at some structs, things like (see struct dvb_demux_feed, at dvb_demux.h): union { struct dmx_ts_feed ts; struct dmx_section_feed sec; } feed; union { dmx_ts_cb ts; dmx_section_cb sec;

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

> >>> I'd leave the decision to the user. We could add a note to the > >>> Documentation/leds/ledtrig-transient.txt that force feedback interface > >>> should be preferable choice for driving vibrate devices. > >>> However only if following conditions are met: > >> > >> What I meant is that it is

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

Hi! > >> However only if following conditions are met: > >> - force feedback driver supports gpio driven devices > >> - there is sample application in tools/input showing how to > >> setup gpio driven vibrate device with use of ff interface > >> - it will be possible to setup vibrate interval

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

On Mon 2017-09-18 22:43:40, Jacek Anaszewski wrote: > Hi, > > On 09/17/2017 07:50 PM, Pavel Machek wrote: > > Hi! > > > Do you think such an improvement could be harmful in some way, > even if it was made optional? > >>> > >>> Of course, we can make LED timing accurate down to