linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: linux-i2c@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Weifeng Voon <weifeng.voon@intel.com>
Subject: Re: [PATCH 3/3] i2c: designware: Find bus speed from ACPI
Date: Tue, 2 Aug 2016 16:43:40 +0200	[thread overview]
Message-ID: <20160802144309.GA1925@katana> (raw)
In-Reply-To: <5e268060-7350-c24a-a53f-c4d9e6b07403@linux.intel.com>

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


> Weifeng's set appears to apply by resolving a single line. But since we both
> need to resend anyway maybe it's easier for you if we post our sets together
> after I resolve conflicts in my patches and do some testing?

That sounds indeed easier and is thus much appreciated.

And welcome back!


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

  reply	other threads:[~2016-08-02 15:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 11:26 [PATCH 0/3] i2c: core/designware: Find bus speed from ACPI Jarkko Nikula
2016-06-06 11:26 ` [PATCH 1/3] i2c: core: Cleanup I2C ACPI namespace Jarkko Nikula
2016-07-14 13:35   ` Wolfram Sang
2016-07-19  4:33     ` Wolfram Sang
2016-06-06 11:26 ` [PATCH 2/3] i2c: core: Add function for finding the bus speed from ACPI Jarkko Nikula
2016-07-14 13:35   ` Wolfram Sang
2016-07-19  4:33     ` Wolfram Sang
2016-06-06 11:26 ` [PATCH 3/3] i2c: designware: Find " Jarkko Nikula
2016-07-14 13:36   ` Wolfram Sang
2016-08-02 14:03     ` Jarkko Nikula
2016-08-02 14:43       ` Wolfram Sang [this message]
2016-06-06 13:24 ` [PATCH 0/3] i2c: core/designware: " Andy Shevchenko
2016-06-06 16:06 ` Mika Westerberg

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=20160802144309.GA1925@katana \
    --to=wsa@the-dreams.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=weifeng.voon@intel.com \
    /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).