netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
	netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH] dt-bindings: net: pse-pd: Fix unusual character in documentation
Date: Tue, 7 Jan 2025 14:55:21 +0000	[thread overview]
Message-ID: <20250107145521.GC5872@kernel.org> (raw)
In-Reply-To: <20250107142659.425877-1-kory.maincent@bootlin.com>

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@bootlin.com>
> ---
> 
> 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@kernel.org>


  reply	other threads:[~2025-01-07 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 14:26 [PATCH] dt-bindings: net: pse-pd: Fix unusual character in documentation Kory Maincent
2025-01-07 14:55 ` Simon Horman [this message]
2025-01-09  3:40 ` patchwork-bot+netdevbpf

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=20250107145521.GC5872@kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=kory.maincent@bootlin.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=robh@kernel.org \
    --cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).