linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Tissoires <benjamin.tissoires@redhat.com>
To: Wolfram Sang <wsa@the-dreams.de>,
	Jonathan Corbet <corbet@lwn.net>, Corey Minyard <minyard@acm.org>,
	Jean Delvare <jdelvare@suse.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andrew Duggan <aduggan@synaptics.com>,
	Christopher Heiny <cheiny@synaptics.com>
Cc: linux-i2c@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: [PATCH v6 0/4] i2c-smbus: add support for HOST NOTIFY
Date: Wed, 16 Mar 2016 17:39:04 +0100	[thread overview]
Message-ID: <1458146348-17171-1-git-send-email-benjamin.tissoires@redhat.com> (raw)

Hi,

this is a quick respin of the series with the kbuild test bot fixes and the
requested lm90 change.

Again, I think applying the RMI4 input driver needs the merge of the input tree
in master first, but having reviews on the Host Notify implementation would be
good.

Cheers,
Benjamin

Benjamin Tissoires (4):
  i2c: add a protocol parameter to the alert callback
  i2c-smbus: add SMBus Host Notify support
  i2c: i801: add support of Host Notify
  Input: synaptics-rmi4 - add SMBus support

 Documentation/i2c/smbus-protocol |   3 +
 drivers/char/ipmi/ipmi_ssif.c    |   6 +-
 drivers/hwmon/lm90.c             |   6 +-
 drivers/i2c/busses/Kconfig       |   1 +
 drivers/i2c/busses/i2c-i801.c    |  85 +++++++-
 drivers/i2c/i2c-smbus.c          | 112 ++++++++++-
 drivers/input/rmi4/Kconfig       |  12 ++
 drivers/input/rmi4/Makefile      |   1 +
 drivers/input/rmi4/rmi_bus.h     |  12 ++
 drivers/input/rmi4/rmi_smbus.c   | 416 +++++++++++++++++++++++++++++++++++++++
 include/linux/i2c-smbus.h        |  44 +++++
 include/linux/i2c.h              |  10 +-
 include/uapi/linux/i2c.h         |   1 +
 13 files changed, 699 insertions(+), 10 deletions(-)
 create mode 100644 drivers/input/rmi4/rmi_smbus.c

-- 
2.5.0

             reply	other threads:[~2016-03-16 16:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 16:39 Benjamin Tissoires [this message]
2016-03-16 16:39 ` [PATCH v6 1/4] i2c: add a protocol parameter to the alert callback Benjamin Tissoires
2016-03-18  0:04   ` Andrew Duggan
2016-03-18  0:50   ` Guenter Roeck
2016-03-18 14:26   ` Corey Minyard
2016-03-16 16:39 ` [PATCH v6 2/4] i2c-smbus: add SMBus Host Notify support Benjamin Tissoires
2016-03-18  0:04   ` Andrew Duggan
2016-03-16 16:39 ` [PATCH v6 3/4] i2c: i801: add support of Host Notify Benjamin Tissoires
2016-03-18  0:05   ` Andrew Duggan
2016-03-16 16:39 ` [PATCH v6 4/4] Input: synaptics-rmi4 - add SMBus support Benjamin Tissoires
2016-03-18  0:06   ` Andrew Duggan
2016-05-31  9:17 ` [PATCH v6 0/4] i2c-smbus: add support for HOST NOTIFY Benjamin Tissoires

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1458146348-17171-1-git-send-email-benjamin.tissoires@redhat.com \
    --to=benjamin.tissoires@redhat.com \
    --cc=aduggan@synaptics.com \
    --cc=cheiny@synaptics.com \
    --cc=corbet@lwn.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=minyard@acm.org \
    --cc=wsa@the-dreams.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).