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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
> 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/