From: Wolfram Sang <wsa@the-dreams.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Guenter Roeck <linux@roeck-us.net>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v4 0/3] i2c: Hookup typec power-negotation to the PMIC and charger
Date: Mon, 4 Sep 2017 15:56:14 +0200 [thread overview]
Message-ID: <20170904135614.w3v3yvrrqructa37@ninjato> (raw)
In-Reply-To: <be26a8cd-e089-0997-2438-5f12ecd02988@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
> I've some other patches pending which require further changes to the
> intel_cht_int33fe driver (*), so I think it would be best if the last
> patch got merged through the platform/x86 tree. The dependencies
> between patch 2-3 are runtime only (and not fatal if missing, just
> inconvenient) so merging this to 2 separate trees should be fine
> as long as both patches get merged for 4.15.
OK. So, I'll just look at the first two patches. You'll know when I done
this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-09-04 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 12:41 [PATCH v4 0/3] i2c: Hookup typec power-negotation to the PMIC and charger Hans de Goede
2017-09-03 12:41 ` [PATCH v4 1/3] i2c: Allow overriding dev_name through board_info Hans de Goede
2017-09-03 12:41 ` [PATCH v4 2/3] i2c-cht-wc: Add device-properties for fusb302 integration Hans de Goede
2017-09-03 12:41 ` [PATCH v4 3/3] platform/x86: intel_cht_int33fe: Update fusb302 type string, add properties Hans de Goede
2017-09-04 6:27 ` Andy Shevchenko
2017-09-04 13:38 ` Hans de Goede
2017-09-04 4:56 ` [PATCH v4 0/3] i2c: Hookup typec power-negotation to the PMIC and charger Wolfram Sang
2017-09-04 13:33 ` Hans de Goede
2017-09-04 13:56 ` Wolfram Sang [this message]
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=20170904135614.w3v3yvrrqructa37@ninjato \
--to=wsa@the-dreams.de \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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).