linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	"Krogerus, Heikki" <heikki.krogerus@linux.intel.com>,
	Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andy@infradead.org>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-i2c <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] i2c: Hookup typec power-negotation to the PMIC and charger
Date: Thu, 19 Oct 2017 16:42:51 +0200	[thread overview]
Message-ID: <20171019144251.hmvkaijwbgamaqoo@katana> (raw)
In-Reply-To: <e875d3d3-d62c-7363-e596-9c0dbeadce5d@redhat.com>

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


> The first patch, although it is an i2c-core change, is really
> quite simple. I believe anyone can review it. But it does need
> someone other then me to take a proper look (and not just do
> a code only review) because it is a core change. Maybe there
> is another way to solve the problem (persistent / predictable
> device-names for i2c devices instantiated through board-data),
> but I don't think so.

My plan is to hopefully meet Mark Brown (SPI and regulator maintainer)
at ELCE next week and have a chat with him about this series. If all
goes well, I'll merge it for v4.15.


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

  reply	other threads:[~2017-10-19 14:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11  9:41 [PATCH v5 0/3] i2c: Hookup typec power-negotation to the PMIC and charger Hans de Goede
2017-10-11  9:41 ` [PATCH resend v5 1/3] i2c: Allow overriding dev_name through board_info Hans de Goede
2017-10-26 20:29   ` Wolfram Sang
2017-10-11  9:41 ` [PATCH resend v5 2/3] i2c-cht-wc: Add device-properties for fusb302 integration Hans de Goede
2017-10-26 20:30   ` Wolfram Sang
2017-10-11  9:41 ` [PATCH resend v5 3/3] platform/x86: intel_cht_int33fe: Update fusb302 type string, add properties Hans de Goede
2017-10-26 20:33   ` Wolfram Sang
2017-10-27 10:13     ` Hans de Goede
2017-10-27 10:31       ` Hans de Goede
2017-10-27 10:41         ` Wolfram Sang
2017-10-27 15:24           ` Hans de Goede
2017-11-03 11:55             ` Andy Shevchenko
2017-10-14 10:45 ` [PATCH v5 0/3] i2c: Hookup typec power-negotation to the PMIC and charger Andy Shevchenko
2017-10-14 12:04   ` Hans de Goede
2017-10-19 14:42     ` Wolfram Sang [this message]
2017-10-19 14:54       ` Hans de Goede
2017-10-20 16:36       ` Andy Shevchenko
2017-10-21  8:33         ` Wolfram Sang
  -- strict thread matches above, loose matches on Subject: below --
2017-09-04 13:47 Hans de Goede

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=20171019144251.hmvkaijwbgamaqoo@katana \
    --to=wsa@the-dreams.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@infradead.org \
    --cc=dvhart@infradead.org \
    --cc=hdegoede@redhat.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.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;
as well as URLs for NNTP newsgroup(s).