From: Krzysztof Kozlowski <krzk@kernel.org>
To: markus.stockhausen@gmx.de, linux-phy@lists.infradead.org,
chris.packham@alliedtelesis.co.nz, devicetree@vger.kernel.org
Subject: Re: AW: [PATCH v2 1/3] dt-bindings: phy: add realtek,otto-serdes PHY binding
Date: Thu, 17 Oct 2024 08:15:43 +0200 [thread overview]
Message-ID: <5ae0ee99-74b2-48db-91c2-8daced6797f5@kernel.org> (raw)
In-Reply-To: <002201db1fe0$4b398dc0$e1aca940$@gmx.de>
On 16/10/2024 17:30, markus.stockhausen@gmx.de wrote:
> Hi Krzysztof,
>
> with your feedback on the latest version I will take up the issues from
> v2 once again. To be sure that I do not miss anything in upcoming v5
> I will comment on all your feedback.
>
>>> ....
>>> Changes in v2:
>>> - new subject
>>> - removed patch command sequences
>>> - renamed parameter controlled-ports to realtek,controlled-ports
>>
>> Changelog goes under ---.
>
> After reading this another 4 times now I think I understand. You mean
> "put changelog below signed-off-by". Will do with next patch.
--- is under Signed-off-by, so yes, but more importantly under ---.
>
>>> ....
>>> diff --git
>>> a/Documentation/devicetree/bindings/phy/realtek,otto-serdes.yaml
>>> b/Documentation/devicetree/bindings/phy/realtek,otto-serdes.yaml
>>> new file mode 100644
>>> index 000000000000..a72ac206b35f
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/phy/realtek,otto-serdes.yaml
>>
>> Nothing improved.
>
> In between renamed to compatible "realtek,rtl8380m-serdes.yaml". I hope
> that fits the requested naming convention.
Yes.
>
>>> + The driver exposes the SerDes registers different from the hardware
>>> + but instead gives a consistent view and programming interface. So
>>> + the RTL838x series has 6 ports and 4 pages, the RTL839x has 14
>>> + ports and 12 pages, the RTL930x has 12 ports and 64 pages and the
>>> + RTL931x has
>>> + 14 ports and 192 pages.
>>
>> Totally messed wrapping. Please wrap your code as Linux coding style.
>
> Was restyled in between. If this is still an issue in latest version, please advise.
It's ok, the rest as well.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-17 6:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 16:36 [PATCH v2 0/3] phy: Realtek Otto SerDes: add new driver Markus Stockhausen
2024-10-07 16:36 ` [PATCH v2 1/3] dt-bindings: phy: add realtek,otto-serdes PHY binding Markus Stockhausen
2024-10-07 18:17 ` Rob Herring (Arm)
2024-10-07 19:26 ` Krzysztof Kozlowski
2024-10-08 5:38 ` AW: " markus.stockhausen
2024-10-08 6:17 ` Krzysztof Kozlowski
2024-10-08 6:56 ` AW: " markus.stockhausen
2024-10-08 8:32 ` Krzysztof Kozlowski
2024-10-08 9:27 ` AW: " markus.stockhausen
2024-10-16 15:30 ` markus.stockhausen
2024-10-17 6:15 ` Krzysztof Kozlowski [this message]
2024-10-07 19:30 ` Rob Herring
2024-10-08 12:27 ` AW: " markus.stockhausen
2024-10-08 7:04 ` Krzysztof Kozlowski
2024-10-08 7:06 ` Krzysztof Kozlowski
2024-10-07 16:36 ` [PATCH v2 2/3] phy: Realtek Otto SerDes driver Markus Stockhausen
2024-10-07 19:32 ` Krzysztof Kozlowski
2024-10-07 16:36 ` [PATCH v2 3/3] phy: Integrate Realtek Otto SerDes driver into build system Markus Stockhausen
2024-10-07 19:27 ` Krzysztof Kozlowski
2024-10-08 6:38 ` kernel test robot
2024-10-08 7:20 ` kernel test robot
2024-10-08 8:21 ` kernel test robot
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=5ae0ee99-74b2-48db-91c2-8daced6797f5@kernel.org \
--to=krzk@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=markus.stockhausen@gmx.de \
/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).