From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfram Sang Subject: Re: [PATCH v7 1/4] i2c: add a protocol parameter to the alert callback Date: Sun, 5 Jun 2016 09:17:28 +0200 Message-ID: <20160605071728.GC2722@katana> References: <1464688985-19102-1-git-send-email-benjamin.tissoires@redhat.com> <1464688985-19102-2-git-send-email-benjamin.tissoires@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YD3LsXFS42OYHhNZ" Return-path: Content-Disposition: inline In-Reply-To: <1464688985-19102-2-git-send-email-benjamin.tissoires@redhat.com> Sender: linux-input-owner@vger.kernel.org To: Benjamin Tissoires Cc: Jonathan Corbet , Corey Minyard , Jean Delvare , Guenter Roeck , Dmitry Torokhov , Andrew Duggan , Christopher Heiny , linux-i2c@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-input@vger.kernel.org List-Id: linux-i2c@vger.kernel.org --YD3LsXFS42OYHhNZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 31, 2016 at 12:03:02PM +0200, Benjamin Tissoires wrote: > .alert() is meant to be generic, but there is currently no way > for the device driver to know which protocol generated the alert. > Add a parameter in .alert() to help the device driver to understand > what is given in data. >=20 > This patch is required to have the support of SMBus Host Notify protocol > through .alert(). >=20 > Tested-by: Andrew Duggan