From: Jakub Kicinski <kuba@kernel.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v5] dt-bindings: net: nxp,sja1105: document spi-cpol/cpha
Date: Tue, 16 May 2023 20:10:00 -0700 [thread overview]
Message-ID: <20230516201000.49216ca0@kernel.org> (raw)
In-Reply-To: <20230515105035.kzmygf2ru2jhusek@skbuf>
On Mon, 15 May 2023 13:50:35 +0300 Vladimir Oltean wrote:
> On Mon, May 15, 2023 at 09:45:25AM +0200, Krzysztof Kozlowski wrote:
> > Some boards use SJA1105 Ethernet Switch with SPI CPHA, while ones with
> > SJA1110 use SPI CPOL, so document this to fix dtbs_check warnings:
> >
> > arch/arm64/boot/dts/freescale/fsl-lx2160a-bluebox3.dtb: ethernet-switch@0: Unevaluated properties are not allowed ('spi-cpol' was unexpected)
> >
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Is my instinct that this should go to net-next correct?
next prev parent reply other threads:[~2023-05-17 3:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 7:45 [PATCH v5] dt-bindings: net: nxp,sja1105: document spi-cpol/cpha Krzysztof Kozlowski
2023-05-15 10:50 ` Vladimir Oltean
2023-05-17 3:10 ` Jakub Kicinski [this message]
2023-05-17 7:01 ` Krzysztof Kozlowski
2023-05-17 7:04 ` Vladimir Oltean
2023-05-17 7:08 ` Vladimir Oltean
2023-05-17 8:23 ` Krzysztof Kozlowski
2023-05-17 8:26 ` Krzysztof Kozlowski
2023-05-17 15:06 ` Jakub Kicinski
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=20230516201000.49216ca0@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).