From: Wolfram Sang <wsa@the-dreams.de>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: linux-i2c@vger.kernel.org, Jean Delvare <jdelvare@suse.de>,
linux-acpi@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/8] i2c: refactor core and break out blocks
Date: Sat, 27 May 2017 18:32:19 +0200 [thread overview]
Message-ID: <20170527163219.ffagajkuzs3naz3g@ninjato> (raw)
In-Reply-To: <8737brn83n.fsf@intel.com>
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
> If you don't mind sending the whole series to the intel-gfx list (Cc'd),
> our CI will run a bunch of tests on it, exercising our use of the I2C
> adapter interfaces for display data channel and I2C over Display Port
> native aux.
Cool, that sounds very helpful! Thanks for the offer, I'll resend the
series there as RFT.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-27 16:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 8:20 [PATCH 0/8] i2c: refactor core and break out blocks Wolfram Sang
2017-05-26 8:20 ` [PATCH 1/8] i2c: rename core source file to allow refactorization Wolfram Sang
2017-05-26 16:12 ` Mika Westerberg
2017-05-29 9:44 ` Jarkko Nikula
2017-05-26 8:20 ` [PATCH 2/8] i2c: break out slave support into seperate file Wolfram Sang
2017-05-26 8:20 ` [PATCH 3/8] i2c: break out smbus " Wolfram Sang
2017-05-26 8:20 ` [PATCH 4/8] i2c: break out OF " Wolfram Sang
2017-05-26 8:20 ` [PATCH 5/8] i2c: break out ACPI " Wolfram Sang
2017-05-26 16:15 ` Mika Westerberg
2017-05-26 8:20 ` [PATCH 6/8] docs: i2c: dev-interface: adapt to new filenames of the i2c core Wolfram Sang
2017-05-26 8:20 ` [PATCH 7/8] i2c: remove unneeded includes from core Wolfram Sang
2017-05-26 8:20 ` [PATCH 8/8] i2c: reformat core-base file header Wolfram Sang
2017-05-27 11:17 ` Andy Shevchenko
2017-05-31 19:05 ` Wolfram Sang
2017-05-26 11:57 ` [PATCH 0/8] i2c: refactor core and break out blocks Jani Nikula
2017-05-27 16:32 ` Wolfram Sang [this message]
2017-05-31 19:07 ` Wolfram Sang
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=20170527163219.ffagajkuzs3naz3g@ninjato \
--to=wsa@the-dreams.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).