public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	platform-driver-x86@vger.kernel.org,
	Hans de Goede <hdegoede@redhat.com>
Subject: [PULL REQUEST] i2c/cht-wc-fusb302-immutable branch for v4.15
Date: Fri, 27 Oct 2017 21:35:51 +0200	[thread overview]
Message-ID: <20171027193546.x5wccdcd7kq3faa6@ninjato> (raw)

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

Hi,

as discussed before, here is the immutable branch for the i2c-cht-wc
driver, so you can safely apply Hans' patch "[PATCH resend v5 3/3]
platform/x86: intel_cht_int33fe: Update fusb302 type string, add
properties" [1] on top of this.

Thanks,

   Wolfram

[1] http://patchwork.ozlabs.org/patch/824314/


The following changes since commit bb176f67090ca54869fc1262c913aa69d2ede070:

  Linux 4.14-rc6 (2017-10-23 06:49:47 -0400)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/cht-wc-fusb302-immutable

for you to fetch changes up to 0224d45c9d46401b6d7018a96cfe049c5da7d91c:

  i2c-cht-wc: Add device-properties for fusb302 integration (2017-10-27 15:51:51 +0200)

----------------------------------------------------------------
Hans de Goede (2):
      i2c: Allow overriding dev_name through board_info
      i2c-cht-wc: Add device-properties for fusb302 integration

 drivers/i2c/busses/Kconfig      |  5 ++++
 drivers/i2c/busses/i2c-cht-wc.c | 51 +++++++++++++++++++++++++++++++++++------
 drivers/i2c/i2c-core-base.c     | 10 ++++++--
 include/linux/i2c.h             |  2 ++
 4 files changed, 59 insertions(+), 9 deletions(-)

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

                 reply	other threads:[~2017-10-27 19:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20171027193546.x5wccdcd7kq3faa6@ninjato \
    --to=wsa@the-dreams.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dvhart@infradead.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@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