linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>, Corey Minyard <minyard@acm.org>,
	Jean Delvare <jdelvare@suse.de>,
	Guenter Roeck <linux@roeck-us.net>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Andrew Duggan <aduggan@synaptics.com>,
	Christopher Heiny <cheiny@synaptics.com>,
	linux-i2c@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v7 0/4] i2c-smbus: add support for HOST NOTIFY
Date: Tue, 7 Jun 2016 16:07:54 +0200	[thread overview]
Message-ID: <20160607140754.GB1505@katana> (raw)
In-Reply-To: <20160607140145.GA19237@mail.corp.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 202 bytes --]


> OK. I'll try to fetch those pending patches on patchwork and see how the
> merge would behave.

Thanks. If you have time for a bit of a reviewing eye on them, this
would also be much appreciated :)


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2016-06-07 14:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 10:03 [PATCH v7 0/4] i2c-smbus: add support for HOST NOTIFY Benjamin Tissoires
2016-05-31 10:03 ` [PATCH v7 1/4] i2c: add a protocol parameter to the alert callback Benjamin Tissoires
2016-06-05  7:17   ` Wolfram Sang
2016-05-31 10:03 ` [PATCH v7 2/4] i2c-smbus: add SMBus Host Notify support Benjamin Tissoires
2016-06-05  7:23   ` Wolfram Sang
2016-05-31 10:03 ` [PATCH v7 3/4] i2c: i801: add support of Host Notify Benjamin Tissoires
2016-06-05  7:25   ` Wolfram Sang
2016-05-31 10:03 ` [PATCH v7 4/4] Input: synaptics-rmi4 - add SMBus support Benjamin Tissoires
2016-06-05  7:13 ` [PATCH v7 0/4] i2c-smbus: add support for HOST NOTIFY Wolfram Sang
2016-06-07 14:01   ` Benjamin Tissoires
2016-06-07 14:07     ` Wolfram Sang [this message]

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=20160607140754.GB1505@katana \
    --to=wsa@the-dreams.de \
    --cc=aduggan@synaptics.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=cheiny@synaptics.com \
    --cc=corbet@lwn.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jdelvare@suse.de \
    --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 \
    /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).