[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <383fda33-143d-9e8e-1f7d-080931ae4496@redhat.com>
Date: Wed, 25 Jan 2023 14:38:59 +0100
From: Hans de Goede <hdegoede@...hat.com>
To: Wolfram Sang <wsa@...nel.org>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
Lee Jones <lee.jones@...aro.org>
Subject: Re: [PATCH resend 0/2] i2c/extcon: intel-cht-wc: Lenovo Yoga Tab 3
Pro YT3-X90F support
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
Powered by blists - more mailing lists