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 06:56:47 +0200 [thread overview]
Message-ID: <20170904045645.fb6scegrypdodvfl@ninjato> (raw)
In-Reply-To: <20170903124156.7440-1-hdegoede@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
Hi,
> The first 2 patches are i2c patches, if you could review and
> merge these (preferably for 4.14, but 4.15 is fine too) that would
> be great.
Definately for v4.15 and I very likely won't be able to review them
before rc1 or rc2 time, if even that. Sorry, but I2C core changes need
extra careful review and I2C maintenance is largely done in my limited
spare time. If you could get other people to review/tag the patches,
this would be very helpful.
> Darren, Andy, the single platform/x86 patch in here should only
> be merged after the 2 i2c patches are in place, otherwise users
> of the board(s) in question will end up not having any battery
> monitoring. Also note that this patch applies on top of the
> "[PATCH v2] platform/x86: intel_cht_int33fe: Work around BIOS bug on some devices"
> patch I send out yesterday.
Is that dependency for v4.14? Would it be an idea if I take the platform
patch via the i2c tree then?
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-04 4: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 ` Wolfram Sang [this message]
2017-09-04 13:33 ` [PATCH v4 0/3] i2c: Hookup typec power-negotation to the PMIC and charger Hans de Goede
2017-09-04 13:56 ` Wolfram Sang
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=20170904045645.fb6scegrypdodvfl@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