From: Hans de Goede <hdegoede@redhat.com>
To: Wolfram Sang <wsa@kernel.org>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH resend 0/2] i2c/extcon: intel-cht-wc: Lenovo Yoga Tab 3 Pro YT3-X90F support
Date: Wed, 25 Jan 2023 14:38:59 +0100 [thread overview]
Message-ID: <383fda33-143d-9e8e-1f7d-080931ae4496@redhat.com> (raw)
In-Reply-To: <Y9Et7nlUmiiPrFUQ@ninjato>
Hi,
On 1/25/23 14:26, Wolfram Sang wrote:
>
>> I'm resending these 2 patches since they seem to have fallen through
>> the cracks.
>
> Which tree should the patches go via? I am assuming not-i2c, but maybe I
> am wrong?
That is a good point. I was under the assumption that the matching MFD
patch, which I did not resend, was already merged. But I'm wrong,
sorry about this.
So I'll do a v2 resend with 3 patches which does include the MFD
patch and then I guess ideally all 3 patches would go through
the MFD tree.
Wolfram, may I/we have your ack for merging the small i2c change
through the MFD tree?
The extcon patch already has an ack for that. So I'll hold of
on sending out a v2 with the missing patch until I have your
ack, so that v2 will be fully ready to merge through the MFD
tree.
Regards,
Hans
next prev parent reply other threads:[~2023-01-25 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 11:12 [PATCH resend 0/2] i2c/extcon: intel-cht-wc: Lenovo Yoga Tab 3 Pro YT3-X90F support Hans de Goede
2023-01-25 11:12 ` [PATCH resend 1/2] i2c: cht-wc: Add charger-chip info for the Lenovo Yoga Tab 3 YT3-X90F Hans de Goede
2023-01-25 11:12 ` [PATCH resend 2/2] extcon: intel-cht-wc: Add support for Lenovo Yoga Tab 3 Pro YT3-X90F Hans de Goede
2023-01-25 13:26 ` [PATCH resend 0/2] i2c/extcon: intel-cht-wc: Lenovo Yoga Tab 3 Pro YT3-X90F support Wolfram Sang
2023-01-25 13:38 ` Hans de Goede [this message]
2023-01-25 13:40 ` 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=383fda33-143d-9e8e-1f7d-080931ae4496@redhat.com \
--to=hdegoede@redhat.com \
--cc=cw00.choi@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=wsa@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