From: Conor Dooley <conor.dooley@microchip.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Conor Dooley <conor@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<chunfeng.yun@mediatek.com>, <gregkh@linuxfoundation.org>,
<conor+dt@kernel.org>, <matthias.bgg@gmail.com>,
<linux@roeck-us.net>, <heikki.krogerus@linux.intel.com>,
<cy_huang@richtek.com>, <linux-usb@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: usb: mt6360-tcpc: Drop interrupt-names
Date: Fri, 26 Jan 2024 09:27:50 +0000 [thread overview]
Message-ID: <20240126-shut-gusto-1da71fd410be@wendy> (raw)
In-Reply-To: <27070454-09e6-422b-95f0-5d674735426b@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
On Fri, Jan 26, 2024 at 10:15:54AM +0100, AngeloGioacchino Del Regno wrote:
> > | required:
> > | - compatible
> > | - interrupts
> > | - interrupt-names
> >
> > It looks like it is a required property after all!
>
> Apparently my brain's binding had
>
> required:
> - blindness
>
> :-P
>
> Yeah, I have no idea why I didn't see that, sorry!
Possibly because your patch never removed it from required in the first
place, if you only looked back at that, and not the binding (or Rob's
bot's report), I can see how you could miss it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Conor Dooley <conor@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<chunfeng.yun@mediatek.com>, <gregkh@linuxfoundation.org>,
<conor+dt@kernel.org>, <matthias.bgg@gmail.com>,
<linux@roeck-us.net>, <heikki.krogerus@linux.intel.com>,
<cy_huang@richtek.com>, <linux-usb@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: usb: mt6360-tcpc: Drop interrupt-names
Date: Fri, 26 Jan 2024 09:27:50 +0000 [thread overview]
Message-ID: <20240126-shut-gusto-1da71fd410be@wendy> (raw)
In-Reply-To: <27070454-09e6-422b-95f0-5d674735426b@collabora.com>
[-- Attachment #1.1: Type: text/plain, Size: 566 bytes --]
On Fri, Jan 26, 2024 at 10:15:54AM +0100, AngeloGioacchino Del Regno wrote:
> > | required:
> > | - compatible
> > | - interrupts
> > | - interrupt-names
> >
> > It looks like it is a required property after all!
>
> Apparently my brain's binding had
>
> required:
> - blindness
>
> :-P
>
> Yeah, I have no idea why I didn't see that, sorry!
Possibly because your patch never removed it from required in the first
place, if you only looked back at that, and not the binding (or Rob's
bot's report), I can see how you could miss it.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-26 9:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 9:41 [PATCH v2 1/2] dt-bindings: usb: mt6360-tcpc: Drop interrupt-names AngeloGioacchino Del Regno
2024-01-19 9:41 ` AngeloGioacchino Del Regno
2024-01-19 9:41 ` [PATCH v2 2/2] usb: typec: tcpci_mt6360: Retrieve interrupt by index AngeloGioacchino Del Regno
2024-01-19 9:41 ` AngeloGioacchino Del Regno
2024-01-19 11:49 ` [PATCH v2 1/2] dt-bindings: usb: mt6360-tcpc: Drop interrupt-names Rob Herring
2024-01-19 11:49 ` Rob Herring
2024-01-19 16:32 ` Conor Dooley
2024-01-19 16:32 ` Conor Dooley
2024-01-22 10:32 ` AngeloGioacchino Del Regno
2024-01-22 10:32 ` AngeloGioacchino Del Regno
2024-01-23 17:14 ` Conor Dooley
2024-01-23 17:14 ` Conor Dooley
2024-01-24 8:48 ` AngeloGioacchino Del Regno
2024-01-24 8:48 ` AngeloGioacchino Del Regno
2024-01-24 16:18 ` Conor Dooley
2024-01-24 16:18 ` Conor Dooley
2024-01-25 10:32 ` Krzysztof Kozlowski
2024-01-25 10:32 ` Krzysztof Kozlowski
2024-01-25 11:41 ` AngeloGioacchino Del Regno
2024-01-25 11:41 ` AngeloGioacchino Del Regno
2024-01-25 16:57 ` Conor Dooley
2024-01-25 16:57 ` Conor Dooley
2024-01-25 17:02 ` Conor Dooley
2024-01-25 17:02 ` Conor Dooley
2024-01-26 9:15 ` AngeloGioacchino Del Regno
2024-01-26 9:15 ` AngeloGioacchino Del Regno
2024-01-26 9:27 ` Conor Dooley [this message]
2024-01-26 9:27 ` Conor Dooley
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=20240126-shut-gusto-1da71fd410be@wendy \
--to=conor.dooley@microchip.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunfeng.yun@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--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.