[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B3D41074B@hasmsx108.ger.corp.intel.com>
Date: Tue, 4 Aug 2015 10:59:52 +0000
From: "Winkler, Tomas" <tomas.winkler@...el.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: "arnd@...db.de" <arnd@...db.de>,
"Usyskin, Alexander" <alexander.usyskin@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [char-misc-next 0/9 RESEND] mei: support for async event
notifications
> > > > 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?
Quoting from (https://lkml.org/lkml/2015/7/23/5) and referring to the second sentence.
'Due to the changes in Linus's tree, this doesn't apply to 4.2-rc3. Can
you refresh this series and resend? Same for the other outstanding mei
patches you have sent that I haven't applied.'
Thanks
Tomas
--
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/
Powered by blists - more mailing lists