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

2015-08-04 Thread Winkler, Tomas
> > > > and consume the event notifications. > > > > The asynchronous nature is provided via poll and fasync. > > > > > > What changed to require a RESEND? > > > > You've asked for it. > > You might want to give me some context, as I have no idea why I asked > for a resend. Obviously you must ha

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

2015-08-03 Thread Greg Kroah-Hartman
On Mon, Jul 27, 2015 at 06:36:18AM +, Winkler, Tomas wrote: > > > > > 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

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

2015-07-26 Thread Winkler, Tomas
> > 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 clien

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

2015-07-26 Thread Greg Kroah-Hartman
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