linux-kernel - Re: [char-misc-next 0/9 RESEND] mei: support for async event notifications

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20150726174527.GB15843@kroah.com>
Date:	Sun, 26 Jul 2015 10:45:27 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Tomas Winkler <tomas.winkler@...el.com>
Cc:	arnd@...db.de, Alexander Usyskin <alexander.usyskin@...el.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [char-misc-next 0/9 RESEND] mei: support for async event
 notifications

On Sun, Jul 26, 2015 at 09:54:14AM +0300, Tomas Winkler wrote:
> FW has gained new capability where a FW client can asynchronously
> notify the host that an event has occurred in its process.
> The notification doesn't provide any data and host may need to query
> further the FW client in order to get details of the event.
> New IOCTLs are introduced for the user space to enable/disable
> and consume the event notifications.
> The asynchronous nature is provided via poll and fasync.

What changed to require a RESEND?
--
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/