On Tue, Jan 07, 2025 at 03:26:59PM +0100, Kory Maincent wrote: > The documentation contained an unusual character due to an issue in my > personal b4 setup. Fix the problem by providing the correct PSE Pinout > Alternatives table number description. > > Signed-off-by: Kory Maincent <kory.maincent@xxxxxxxxxxx> > --- > > I don't use net-next prefix as I suppose it would go in the devicetree > tree. > > .../devicetree/bindings/net/pse-pd/pse-controller.yaml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml b/Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml > index a12cda8aa764..cd09560e0aea 100644 > --- a/Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml > +++ b/Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml > @@ -81,7 +81,7 @@ properties: > List of phandles, each pointing to the power supply for the > corresponding pairset named in 'pairset-names'. This property > aligns with IEEE 802.3-2022, Section 33.2.3 and 145.2.4. > - PSE Pinout Alternatives (as per IEEE 802.3-2022 Table 145\u20133) > + PSE Pinout Alternatives (as per IEEE 802.3-2022 Table 145-3) FWIIW, I checked and unicode character 2013 is an En Dash. So this looks good to me. > |-----------|---------------|---------------|---------------|---------------| > | Conductor | Alternative A | Alternative A | Alternative B | Alternative B | > | | (MDI-X) | (MDI) | (X) | (S) | Reviewed-by: Simon Horman <horms@xxxxxxxxxx>
