From: Hans de Goede <hdegoede@redhat.com>
To: Darren Hart <dvhart@infradead.org>
Cc: Wolfram Sang <wsa@the-dreams.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>,
linux-i2c@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v5 0/4] i2c-core improvements for acpi devices + ACPI INT33FE driver
Date: Fri, 14 Apr 2017 14:34:16 +0200 [thread overview]
Message-ID: <1a01f3d0-3d14-9f93-e789-cf1f0232becc@redhat.com> (raw)
In-Reply-To: <20170413190933.GA9783@fury>
Hi,
On 13-04-17 21:09, Darren Hart wrote:
> On Wed, Apr 05, 2017 at 12:03:31AM +0200, Hans de Goede wrote:
>> Hi All,
>>
>> Here is v5 of my patch-set for my i2c-core improvements for acpi
>> devices + the ACPI INT33FE platform driver.
>>
>> New in this version are some minor fixed to the INT33FE driver.
>>
>> The INT33FE driver depends on the i2c-core changes, so if
>> it is ok with Darren / Andy I believe it would be best for
>> this driver to be merged through the i2c subsys tree (with
>> their ack).
>
> Is there an immutable i2c branch I can merge with these changes in order to add
> the Cherry Trail driver on top of those?
The i2c-core patches have been reviewed, but to the best of my
knowledge they have not been merged yet.
Wolfram, what is the status of this ?
Regards,
Hans
prev parent reply other threads:[~2017-04-14 12:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 22:03 [PATCH v5 0/4] i2c-core improvements for acpi devices + ACPI INT33FE driver Hans de Goede
2017-04-04 22:03 ` [PATCH v5 1/4] i2c: core: Allow getting ACPI info by index Hans de Goede
2017-04-16 20:08 ` Wolfram Sang
2017-04-04 22:03 ` [PATCH v5 2/4] i2c: core: Add new i2c_acpi_new_device helper function Hans de Goede
2017-04-16 20:08 ` Wolfram Sang
2017-04-04 22:03 ` [PATCH v5 3/4] i2c: core: Allow drivers to disable i2c-core irq mapping Hans de Goede
2017-04-05 13:31 ` Andy Shevchenko
2017-04-16 20:08 ` Wolfram Sang
2017-04-04 22:03 ` [PATCH v5 4/4] platform/x86: Add Intel Cherry Trail ACPI INT33FE device driver Hans de Goede
2017-04-05 13:52 ` Andy Shevchenko
2017-04-05 15:41 ` Darren Hart
2017-04-16 20:08 ` Wolfram Sang
2017-04-17 22:40 ` Darren Hart
2017-04-13 19:09 ` [PATCH v5 0/4] i2c-core improvements for acpi devices + ACPI INT33FE driver Darren Hart
2017-04-14 12:34 ` Hans de Goede [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=1a01f3d0-3d14-9f93-e789-cf1f0232becc@redhat.com \
--to=hdegoede@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dvhart@infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=wsa@the-dreams.de \
/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).