linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Phil Reid <preid@electromag.com.au>,
	jarkko.nikula@linux.intel.com, mika.westerberg@linux.intel.com,
	wsa@the-dreams.de, tim@krieglstein.org,
	linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2 0/2] i2c: designware: add i2c gpio recovery option
Date: Tue, 29 Aug 2017 19:28:02 +0300	[thread overview]
Message-ID: <1504024082.25945.149.camel@linux.intel.com> (raw)
In-Reply-To: <1503575995.25945.82.camel@linux.intel.com>

On Thu, 2017-08-24 at 14:59 +0300, Andy Shevchenko wrote:
> On Thu, 2017-08-24 at 17:21 +0800, Phil Reid wrote:
> > On 16/06/2017 15:42, Phil Reid wrote:

> > Any comments on these 2 patches?
> 
> Oops, overloaded. I will do latest next week. I would like to massage
> a
> bit this and see the result.

I have applied these to my tree (based on linux-next). It required some
work and still requires more.

Care to rebase to latest i2c-next tree and send as v3?

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2017-08-29 16:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16  7:42 [PATCH v2 0/2] i2c: designware: add i2c gpio recovery option Phil Reid
2017-06-16  7:42 ` [PATCH v2 1/2] i2c: Switch to using gpiod interface for gpio bus recovery Phil Reid
2017-06-16  7:42 ` [PATCH v2 2/2] i2c: designware: add i2c gpio recovery option Phil Reid
2017-08-24  9:21 ` [PATCH v2 0/2] " Phil Reid
2017-08-24 11:59   ` Andy Shevchenko
2017-08-29 16:28     ` Andy Shevchenko [this message]
2017-08-30  6:18       ` Phil Reid

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=1504024082.25945.149.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=preid@electromag.com.au \
    --cc=tim@krieglstein.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).