linux-kernel - Re: A desktop environment[1] kernel wishlist

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALAqxLUdkpwg=+Fcz+BKTAb1uzYbeSU0M6o5FcZGOD8X37Dfzw@mail.gmail.com>
Date:	Tue, 28 Oct 2014 07:36:24 -0700
From:	John Stultz <john.stultz@...aro.org>
To:	Bastien Nocera <hadess@...ess.net>
Cc:	Zygo Blaxell <zblaxell@...ryterror.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: A desktop environment[1] kernel wishlist

On Tue, Oct 28, 2014 at 5:36 AM, Bastien Nocera <hadess@...ess.net> wrote:
> Maybe the wake-up reason isn't good enough on its own, but how do I know
> which one the possible wake-up reasons was the last one to trigger?

So I feel like I'm still missing why its so critical to know what the
last-event was?  To me it seems a number of events have occurred, and
they should all be processed. Since they're all asynchronous, they
could come in any order, so it seems best handle them one by one
rather then have any requirement on which one happened last.

What does the exact timeline of the events provide for you?

thanks
-john
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/