All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: devicetree@vger.kernel.org, andrew@lunn.ch,
	alexandre.belloni@bootlin.com, linux-phy@lists.infradead.org,
	vkoul@kernel.org, robh+dt@kernel.org, kishon@ti.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: phy: Add lan966x-serdes binding
Date: Wed, 27 Oct 2021 15:37:16 -0500	[thread overview]
Message-ID: <YXm4fIRt4NHo7z0F@robh.at.kernel.org> (raw)
In-Reply-To: <20211020094229.1760793-2-horatiu.vultur@microchip.com>

On Wed, 20 Oct 2021 11:42:27 +0200, Horatiu Vultur wrote:
> Document the lan966x ethernet serdes phy driver bindings.
> 
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
>  .../phy/microchip,lan966x-serdes.yaml         | 59 +++++++++++++++++++
>  1 file changed, 59 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/phy/microchip,lan966x-serdes.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: devicetree@vger.kernel.org, andrew@lunn.ch,
	alexandre.belloni@bootlin.com, linux-phy@lists.infradead.org,
	vkoul@kernel.org, robh+dt@kernel.org, kishon@ti.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: phy: Add lan966x-serdes binding
Date: Wed, 27 Oct 2021 15:37:16 -0500	[thread overview]
Message-ID: <YXm4fIRt4NHo7z0F@robh.at.kernel.org> (raw)
In-Reply-To: <20211020094229.1760793-2-horatiu.vultur@microchip.com>

On Wed, 20 Oct 2021 11:42:27 +0200, Horatiu Vultur wrote:
> Document the lan966x ethernet serdes phy driver bindings.
> 
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
>  .../phy/microchip,lan966x-serdes.yaml         | 59 +++++++++++++++++++
>  1 file changed, 59 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/phy/microchip,lan966x-serdes.yaml
> 

Reviewed-by: Rob Herring <robh@kernel.org>

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  reply	other threads:[~2021-10-27 20:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20  9:42 [PATCH v4 0/3] phy: Add driver for lan966x Serdes driver Horatiu Vultur
2021-10-20  9:42 ` Horatiu Vultur
2021-10-20  9:42 ` [PATCH v4 1/3] dt-bindings: phy: Add lan966x-serdes binding Horatiu Vultur
2021-10-20  9:42   ` Horatiu Vultur
2021-10-27 20:37   ` Rob Herring [this message]
2021-10-27 20:37     ` Rob Herring
2021-10-20  9:42 ` [PATCH v4 2/3] dt-bindings: phy: Add constants for lan966x serdes Horatiu Vultur
2021-10-20  9:42   ` Horatiu Vultur
2021-10-27 20:37   ` Rob Herring
2021-10-27 20:37     ` Rob Herring
2021-10-20  9:42 ` [PATCH v4 3/3] phy: Add lan966x ethernet serdes PHY driver Horatiu Vultur
2021-10-20  9:42   ` Horatiu Vultur
2021-11-04  8:58 ` [PATCH v4 0/3] phy: Add driver for lan966x Serdes driver Horatiu Vultur
2021-11-04  8:58   ` Horatiu Vultur

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=YXm4fIRt4NHo7z0F@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=horatiu.vultur@microchip.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.