From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ilya Orazov <ilordash02@gmail.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Aswath Govindraju <a-govindraju@ti.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
linux-can@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/1] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6561
Date: Wed, 14 Aug 2024 11:03:47 +0200 [thread overview]
Message-ID: <eb04b684-eccd-4952-a310-022d00b50a55@kernel.org> (raw)
In-Reply-To: <CAGCz5Hk=mSjQ1eFWstQQu=JZUkavJ_mRhnp8DRELUXP_syq4Zw@mail.gmail.com>
On 13/08/2024 19:14, Ilya Orazov wrote:
>> '#phy-cells':
>> const: 0
>>
>> base-commit: 6a0e38264012809afa24113ee2162dc07f4ed22b
>> --
>> 2.34.1
>>
>
> Could you please review my patch?
You received review. Why do you ping after few days?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-14 9:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 21:03 [PATCH 0/2] phy: Add support for Microchip ATA6561 CAN Transceiver Ilya Orazov
2024-07-18 21:03 ` [PATCH 1/2] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6561 Ilya Orazov
2024-07-19 15:07 ` Conor Dooley
2024-07-23 17:20 ` IlorDash
2024-07-23 18:50 ` Conor Dooley
2024-07-23 19:55 ` Ilya Orazov
2024-07-23 20:14 ` Conor Dooley
2024-07-28 8:52 ` Ilya Orazov
2024-07-29 8:51 ` Geert Uytterhoeven
2024-08-01 15:12 ` Conor Dooley
2024-08-03 12:31 ` Ilya Orazov
2024-08-05 10:11 ` Conor Dooley
2024-08-07 18:02 ` [PATCH v2 0/1] phy: Add support for Microchip ATA6561 CAN Transceiver Ilya Orazov
2024-08-07 18:02 ` [PATCH v2 1/1] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6561 Ilya Orazov
2024-08-07 18:09 ` [PATCH v2 0/1] phy: Add support for Microchip ATA6561 CAN Transceiver Ilya Orazov
2024-08-07 18:09 ` [PATCH v2 1/1] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6561 Ilya Orazov
2024-08-07 19:12 ` Rob Herring (Arm)
2024-08-08 15:48 ` Conor Dooley
2024-08-08 16:40 ` Krzysztof Kozlowski
2024-08-08 19:17 ` [PATCH v3 " Ilya Orazov
2024-08-09 14:57 ` Conor Dooley
2024-08-13 17:14 ` Ilya Orazov
2024-08-14 9:03 ` Krzysztof Kozlowski [this message]
2024-08-14 16:56 ` Ilya Orazov
2024-07-18 21:03 ` [PATCH 2/2] phy: phy-can-transceiver: Add support for " Ilya Orazov
-- strict thread matches above, loose matches on Subject: below --
2024-08-21 21:53 [PATCH v3 0/1] dt-bindings: phy: ti,tcan104x-can: Document Microchip Ilya Orazov
2024-08-21 21:53 ` [PATCH v3 1/1] dt-bindings: phy: ti,tcan104x-can: Document Microchip ATA6561 Ilya Orazov
2024-08-22 7:10 ` Krzysztof Kozlowski
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=eb04b684-eccd-4952-a310-022d00b50a55@kernel.org \
--to=krzk@kernel.org \
--cc=a-govindraju@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ilordash02@gmail.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=robh@kernel.org \
--cc=vkoul@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).