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

From: Greg Kroah-Hartman
Date: Mon Aug 03 2015 - 20:19:02 EST


On Mon, Jul 27, 2015 at 06:36:18AM +0000, 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 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?
>
> 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 have done something to the series from
the previous one, right?

thanks,

greg "short term memory of a squirrel" k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/