From: Conor Dooley <conor.dooley@microchip.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Frank Li <Frank.li@nxp.com>, <robh@kernel.org>,
<alexandre.belloni@bootlin.com>, <conor.culhane@silvaco.com>,
<gregkh@linuxfoundation.org>, <imx@lists.linux.dev>,
<jirislaby@kernel.org>, <joe@perches.com>,
<linux-i3c@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-serial@vger.kernel.org>, <miquel.raynal@bootlin.com>,
<zbigniew.lukwinski@linux.intel.com>,
<devicetree@vger.kernel.org>, <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH v2 2/7] dt-bindings: i3c: svc: add compatible string i3c: silvaco,i3c-target-v1
Date: Tue, 16 Jan 2024 09:30:25 +0000 [thread overview]
Message-ID: <20240116-bleach-herbicide-48d636967134@wendy> (raw)
In-Reply-To: <d45e31c4-914e-4cea-a145-9775b6f516ab@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
On Tue, Jan 16, 2024 at 08:24:20AM +0100, Krzysztof Kozlowski wrote:
> On 16/01/2024 03:29, Frank Li wrote:
> >>> Patches were accepted after discussion, what you ponit to. So I
> >>> think everyone agree on the name 'silvaco,i3c-master-v1'.
> >>> I plan send next version to fix auto build error. Any additional
> >>> comments about this?
> >>
> >> I still do not see how did you address Rob's comment and his point is
> >> valid. You just did not reply to it.
> >
> > See https://lore.kernel.org/imx/ZXCiaKfMYYShoiXK@lizhi-Precision-Tower-5810/
>
> First of all, that's not the answer to Rob's email, but some other
> thread which is 99% ignored by Rob (unless he has filters for
> "@Rob"...). Therefore no, it does not count as valid answer.
>
> Second, explanation does not make sense. There is no argument granting
> you exception from SoC specific compatibles.
The patch could have been applied two months ago had Frank done as
was requested (multiple times). I don't understand the resistance
towards doing so given the process has taken way way longer as a result.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-01-16 9:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 17:52 [PATCH v2 0/7] I3C target mode support Frank Li
2024-01-10 17:52 ` [PATCH v2 1/7] i3c: add " Frank Li
2024-01-10 17:52 ` [PATCH v2 2/7] dt-bindings: i3c: svc: add compatible string i3c: silvaco,i3c-target-v1 Frank Li
2024-01-12 7:38 ` Krzysztof Kozlowski
2024-01-12 15:31 ` Frank Li
2024-01-12 15:50 ` Krzysztof Kozlowski
2024-01-12 16:00 ` Krzysztof Kozlowski
2024-01-12 16:06 ` Frank Li
2024-01-15 19:44 ` Frank Li
2024-01-15 20:38 ` Krzysztof Kozlowski
2024-01-16 2:29 ` Frank Li
2024-01-16 7:24 ` Krzysztof Kozlowski
2024-01-16 9:30 ` Conor Dooley [this message]
2024-01-16 9:33 ` Krzysztof Kozlowski
2024-01-16 9:48 ` Conor Dooley
2024-01-16 17:35 ` Frank Li
2024-01-16 18:23 ` Conor Dooley
2024-01-16 19:13 ` Frank Li
2024-01-16 20:30 ` Krzysztof Kozlowski
2024-01-16 20:44 ` Frank Li
2024-01-16 20:56 ` Krzysztof Kozlowski
2024-01-16 21:01 ` Krzysztof Kozlowski
2024-01-16 22:25 ` Frank Li
2024-01-17 6:50 ` Krzysztof Kozlowski
2024-01-17 16:19 ` Frank Li
2024-01-17 17:15 ` Krzysztof Kozlowski
2024-01-17 18:06 ` Frank Li
2024-01-19 17:13 ` Frank Li
2024-01-16 21:31 ` Frank Li
2024-01-17 6:45 ` Krzysztof Kozlowski
2024-01-10 17:52 ` [PATCH v2 3/7] Documentation: i3c: Add I3C target mode controller and function Frank Li
2024-01-11 23:45 ` kernel test robot
2024-01-10 17:52 ` [PATCH v2 4/7] i3c: target: add svc target controller support Frank Li
2024-01-11 10:01 ` kernel test robot
2024-01-11 13:49 ` kernel test robot
2024-01-10 17:52 ` [PATCH v2 5/7] i3c: target: func: add tty driver Frank Li
2024-01-10 17:52 ` [PATCH v2 6/7] i3c: add API i3c_dev_gettstatus_format1() to get target device status Frank Li
2024-01-10 17:52 ` [PATCH v2 7/7] tty: i3c: add TTY over I3C master support Frank Li
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=20240116-bleach-herbicide-48d636967134@wendy \
--to=conor.dooley@microchip.com \
--cc=Frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor.culhane@silvaco.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jirislaby@kernel.org \
--cc=joe@perches.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=robh@kernel.org \
--cc=zbigniew.lukwinski@linux.intel.com \
/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