From: "Duje Mihanović" <duje.mihanovic@skole.hr>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Lubomir Rintel <lkundrak@v3.sk>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] arm: marvell: Fix maxium->maxim typo for brownstone dts
Date: Fri, 25 Aug 2023 23:06:29 +0200 [thread overview]
Message-ID: <4825493.GXAFRqVoOG@radijator> (raw)
In-Reply-To: <7336acfc-eea8-472c-8b04-c04b4c401fe8@lunn.ch>
On Tuesday, August 22, 2023 1:43:08 AM CEST Andrew Lunn wrote:
> Maybe a dumb question. Does I2C core still ignore the vendor part? Its
> a long time since i did anything with i2c, but i thought for
> historical reasons it ignore the vendor?
>
> If this is still true, then yes, this is just a spelling
> error. However, if the vendor is being used to match device to driver,
> this is more than a spelling issue, and should be directed to stable.
I have just tested this by changing the MUIC compatible on my (not yet
upstreamed) samsung,coreprimevelte board from "siliconmitus,sm5504-muic" to
"siliconnitus,sm5504-muic". With this change USB no longer works, presumably
because USB probing gets deferred forever since this MUIC referenced in USB's
extcon never gets probed.
I assume this PMIC would behave identically and thus this should go to stable.
Would this be done by sending a v2 with the Cc: tag added?
Regards,
Duje
next prev parent reply other threads:[~2023-08-25 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 20:09 [PATCH RESEND] arm: marvell: Fix maxium->maxim typo for brownstone dts Duje Mihanović
2023-08-21 20:09 ` Duje Mihanović
2023-08-21 23:43 ` Andrew Lunn
2023-08-21 23:43 ` Andrew Lunn
2023-08-25 21:06 ` Duje Mihanović [this message]
2023-08-26 3:31 ` Andrew Lunn
2023-08-26 3:31 ` Andrew Lunn
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=4825493.GXAFRqVoOG@radijator \
--to=duje.mihanovic@skole.hr \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.