From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-i2c@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH v2 0/3] i2c: designware-pci: refactor and add Merrifield support
Date: Thu, 16 Jun 2016 10:44:21 +0300 [thread overview]
Message-ID: <a653f0b3-0a95-8227-db35-0076c1461827@linux.intel.com> (raw)
In-Reply-To: <1466003107-19375-1-git-send-email-andriy.shevchenko@linux.intel.com>
On 06/15/2016 06:05 PM, Andy Shevchenko wrote:
> Tested on bare metal (Intel Edison) by enumerating I2C GPIO expanders.
>
> In v2:
> - leave bus 3 at STD speed for Medfield
> - be consistent with workflow, i.e. call ->setup, and _then_ assign to i2c
> properties
> - add a comment to explain magic numbers for Merrifield
> - add an Ack for patch 3
>
> Andy Shevchenko (3):
> i2c: designware-pci: Make bus number allocation robust
> i2c: designware-pci: Introduce Merrifield support
> i2c: designware-pci: Sort header block alphabetically
>
> drivers/i2c/busses/i2c-designware-core.h | 1 +
> drivers/i2c/busses/i2c-designware-pcidrv.c | 143 +++++++++++++++++------------
> 2 files changed, 86 insertions(+), 58 deletions(-)
>
> --
> 2.8.1
>
To the series (patch 3 has my ack already):
Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
next prev parent reply other threads:[~2016-06-16 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 15:05 [PATCH v2 0/3] i2c: designware-pci: refactor and add Merrifield support Andy Shevchenko
2016-06-15 15:05 ` [PATCH v2 1/3] i2c: designware-pci: Make bus number allocation robust Andy Shevchenko
2016-06-15 15:05 ` [PATCH v2 2/3] i2c: designware-pci: Introduce Merrifield support Andy Shevchenko
2016-06-15 15:05 ` [PATCH v2 3/3] i2c: designware-pci: Sort header block alphabetically Andy Shevchenko
2016-06-16 7:44 ` Jarkko Nikula [this message]
2016-06-19 17:42 ` [PATCH v2 0/3] i2c: designware-pci: refactor and add Merrifield support Wolfram Sang
2016-06-19 18:08 ` Andy Shevchenko
2016-06-19 18:17 ` 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=a653f0b3-0a95-8227-db35-0076c1461827@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--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).