devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: michael@walle.cc
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	netdev@vger.kernel.org, robh@kernel.org, f.fainelli@gmail.com,
	simon.horman@netronome.com, andrew@lunn.ch,
	o.rempel@pengutronix.de
Subject: Re: [PATCH v2 0/6] net: phy: at803x device tree binding
Date: Wed, 06 Nov 2019 21:42:22 -0800 (PST)	[thread overview]
Message-ID: <20191106.214222.912233743829797849.davem@davemloft.net> (raw)
In-Reply-To: <20191106223617.1655-1-michael@walle.cc>

From: Michael Walle <michael@walle.cc>
Date: Wed,  6 Nov 2019 23:36:11 +0100

> Adds a device tree binding to configure the clock and the RGMII voltage.
 ...

Series applied, thank you.

      parent reply	other threads:[~2019-11-07  5:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 22:36 [PATCH v2 0/6] net: phy: at803x device tree binding Michael Walle
2019-11-06 22:36 ` [PATCH v2 1/6] net: phy: at803x: fix Kconfig description Michael Walle
2019-11-07  1:50   ` Andrew Lunn
2019-11-06 22:36 ` [PATCH v2 2/6] dt-bindings: net: phy: Add support for AT803X Michael Walle
2019-11-07  1:51   ` Andrew Lunn
2019-11-06 22:36 ` [PATCH v2 3/6] net: phy: at803x: add device tree binding Michael Walle
2019-11-06 22:36 ` [PATCH v2 4/6] net: phy: at803x: mention AR8033 as same as AR8031 Michael Walle
2019-11-07  2:04   ` Andrew Lunn
2019-11-07  7:47     ` Michael Walle
2019-11-07 12:55       ` Andrew Lunn
2019-11-07 14:28         ` Michael Walle
2019-11-06 22:36 ` [PATCH v2 5/6] net: phy: at803x: fix the PHY names Michael Walle
2019-11-07  2:05   ` Andrew Lunn
2019-11-06 22:36 ` [PATCH v2 6/6] net: phy: at803x: remove config_init for AR9331 Michael Walle
2019-11-07  2:05   ` Andrew Lunn
2019-11-07  5:42 ` David Miller [this message]

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=20191106.214222.912233743829797849.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=simon.horman@netronome.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).