From: Jani Nikula <jani.nikula@linux.intel.com>
To: Wolfram Sang <wsa@the-dreams.de>, intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: warning for i2c: refactor core and break out blocks
Date: Mon, 29 May 2017 11:41:00 +0300 [thread overview]
Message-ID: <87inkkkqcj.fsf@intel.com> (raw)
In-Reply-To: <20170527172737.jbvi4unf5tpr5sbc@ninjato>
On Sat, 27 May 2017, Wolfram Sang <wsa@the-dreams.de> wrote:
> As far as I can read the above page, all non-green blocks are caused by
> non-I2C issues. So, I'd assume my patch set doesn't break things. Good!
Thanks for submitting the series for testing. This is just a basic test
set, but gives confidence there's nothing terribly wrong here. :)
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-05-29 8:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 16:40 [RFT 0/8] i2c: refactor core and break out blocks Wolfram Sang
2017-05-27 16:40 ` [RFT 1/8] i2c: rename core source file to allow refactorization Wolfram Sang
2017-05-27 16:40 ` [RFT 2/8] i2c: break out slave support into seperate file Wolfram Sang
2017-05-27 16:40 ` [RFT 3/8] i2c: break out smbus " Wolfram Sang
2017-05-27 16:40 ` [RFT 4/8] i2c: break out OF " Wolfram Sang
2017-05-27 16:40 ` [RFT 5/8] i2c: break out ACPI " Wolfram Sang
2017-05-27 16:40 ` [RFT 6/8] docs: i2c: dev-interface: adapt to new filenames of the i2c core Wolfram Sang
2017-05-27 16:40 ` [RFT 7/8] i2c: remove unneeded includes from core Wolfram Sang
2017-05-27 16:40 ` [RFT 8/8] i2c: reformat core-base file header Wolfram Sang
2017-05-27 16:58 ` ✗ Fi.CI.BAT: warning for i2c: refactor core and break out blocks Patchwork
2017-05-27 17:27 ` Wolfram Sang
2017-05-29 8:41 ` Jani Nikula [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=87inkkkqcj.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.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