On Fri, 2 Sep 2016 10:26:33 -0700
Eric Holscher wrote:
> I'm happy to resend the whole patch, or feel free to simply edit my
> original with your suggested
> ``app.add_stylesheet('theme_overrides.css')`` line.
Please go ahead and send an updated patch. Then I'm sure I'll manage to
find some tim
On 09/02/2016 04:33 PM, Alan Stern wrote:
On Fri, 2 Sep 2016, Jacek Anaszewski wrote:
I'm pretty sure noone ever planned to have more than 1 trigger
assigned to a single LED. I just realized there will be a problem with
proposed solution: sysfs files conflict.
...
Currently we support only
On Sat, 3 Sep 2016, Jacek Anaszewski wrote:
> >>> Maybe it would make more sense, in this case, to allow only three
> >>> possibilities for a USB port activity trigger. Toggle the LED
> >>> whenever:
> >>>
> >>> There is activity on the specified port, or
> >>>
> >>> There is any activity on
On Tue, Aug 30, 2016 at 02:17:27PM -0400, Chris Metcalf wrote:
> On 8/30/2016 1:36 PM, Chris Metcalf wrote:
> >>>See the other thread with Peter Z for the longer discussion of this.
> >>>At this point I'm leaning towards replacing the set_tsk_need_resched() with
> >>>
> >>> set_current_state(TA
On Fri, Sep 02, 2016 at 09:41:18PM -0700, Linus Torvalds wrote:
> On Sep 2, 2016 9:20 PM, "Dmitry Torokhov" wrote:
> >
> > Like what? Some devices do need to have firmware loaded so we know
> > their capabilities, so we really can't push the firmware loading into
> > "open".
>
> So you
> (a) docu
On Sat, Sep 3, 2016 at 11:01 AM, Linus Torvalds
wrote:
> On Sat, Sep 3, 2016 at 10:49 AM, Dmitry Torokhov
> wrote:
>>
>> Unfortunately module loading and availability of firmware is very
>> loosely coupled.
>
> The whole "let's add a new magical proc entry to say that all
> filesystems are mounte
On Sat, Sep 3, 2016 at 10:49 AM, Dmitry Torokhov
wrote:
>
> Unfortunately module loading and availability of firmware is very
> loosely coupled.
The whole "let's add a new magical proc entry to say that all
filesystems are mounted" is all about the user space coupling them.
I'm just saying that
On 09/03/2016 05:17 PM, Alan Stern wrote:
On Sat, 3 Sep 2016, Jacek Anaszewski wrote:
Maybe it would make more sense, in this case, to allow only three
possibilities for a USB port activity trigger. Toggle the LED
whenever:
There is activity on the specified port, or
There is
On Sat, 3 Sep 2016, Jacek Anaszewski wrote:
> >> The remaining issue is the sysfs interface design for defining and
> >> presenting multiple USB ports. I'm still in favour of a single
> >> attribute with space separated list. This scheme is commonly used
> >> in existing interfaces.
> >
> > No suc
>> NAK, just noise.
>
> And frankly I hate that leading space.
Would you like to comment the recent update of the document "CodingStyle" any
more?
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/Documentation/CodingStyle?id=865a1caa4b6b886babdd9d67e7c3608be4567a51
Regard
From: SF Markus Elfring
Date: Sun, 4 Sep 2016 08:50:20 +0200
>>> NAK, just noise.
>>
>> And frankly I hate that leading space.
>
> Would you like to comment the recent update of the document "CodingStyle" any
> more?
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/Doc
11 matches
Mail list logo