Hi All,

I'm resending these 2 patches since they seem to have fallen through
the cracks.

Regards,

Hans


Hans de Goede (2):
  i2c: cht-wc: Add charger-chip info for the Lenovo Yoga Tab 3 YT3-X90F
  extcon: intel-cht-wc: Add support for Lenovo Yoga Tab 3 Pro YT3-X90F

 drivers/extcon/extcon-intel-cht-wc.c |  1 +
 drivers/i2c/busses/i2c-cht-wc.c      | 46 ++++++++++++++++++++++++++++
 2 files changed, 47 insertions(+)

-- 
2.39.0

> 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?

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

> Wolfram, may I/we have your ack for merging the small i2c change
> through the MFD tree?

Patch 1 already has my ack :)