From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755274AbbGZRp3 (ORCPT ); Sun, 26 Jul 2015 13:45:29 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:53276 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755191AbbGZRp2 (ORCPT ); Sun, 26 Jul 2015 13:45:28 -0400 Date: Sun, 26 Jul 2015 10:45:27 -0700 From: Greg Kroah-Hartman To: Tomas Winkler Cc: arnd@arndb.de, Alexander Usyskin , linux-kernel@vger.kernel.org Subject: Re: [char-misc-next 0/9 RESEND] mei: support for async event notifications Message-ID: <20150726174527.GB15843@kroah.com> References: <1437893663-2068-1-git-send-email-tomas.winkler@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1437893663-2068-1-git-send-email-tomas.winkler@intel.com> User-Agent: Mutt/1.5.23+102 (2ca89bed6448) (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?