All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: martin.blumenstingl@googlemail.com
Cc: linux-amlogic@lists.infradead.org, netdev@vger.kernel.org,
	khilman@baylibre.com, carlo@caione.org, jbrunet@baylibre.com,
	narmstrong@baylibre.com
Subject: Re: [net-next PATCH v1 0/3] dwmac-meson8b: small cleanup
Date: Mon, 19 Feb 2018 11:27:00 -0500 (EST)	[thread overview]
Message-ID: <20180219.112700.346909623772944138.davem@davemloft.net> (raw)
In-Reply-To: <20180217140820.30257-1-martin.blumenstingl@googlemail.com>

From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Date: Sat, 17 Feb 2018 15:08:17 +0100

> This is a follow-up to my previous series "dwmac-meson8b: clock fixes for
> Meson8b" from [0].
> during the review of that series it was found that the clock registration
> could be simplified. now that the previous series has landed we can start
> cleaning up the clock registration.
> 
> the goal of this series is to simplify the code in the dwmac-meson8b
> driver. no functional changes are intended.
> 
> I have tested this on my Khadas VIM2 (GXM SoC, with RGMII PHY) and my
> Endless Mini (EC-100, Meson8b SoC with RMII PHY, .dts support is not part
> of mainline yet). no problems were found.
> 
> 
> [0] http://lists.infradead.org/pipermail/linux-amlogic/2018-January/006143.html

Series applied, thank you very much.

WARNING: multiple messages have this Message-ID (diff)
From: davem@davemloft.net (David Miller)
To: linus-amlogic@lists.infradead.org
Subject: [net-next PATCH v1 0/3] dwmac-meson8b: small cleanup
Date: Mon, 19 Feb 2018 11:27:00 -0500 (EST)	[thread overview]
Message-ID: <20180219.112700.346909623772944138.davem@davemloft.net> (raw)
In-Reply-To: <20180217140820.30257-1-martin.blumenstingl@googlemail.com>

From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Date: Sat, 17 Feb 2018 15:08:17 +0100

> This is a follow-up to my previous series "dwmac-meson8b: clock fixes for
> Meson8b" from [0].
> during the review of that series it was found that the clock registration
> could be simplified. now that the previous series has landed we can start
> cleaning up the clock registration.
> 
> the goal of this series is to simplify the code in the dwmac-meson8b
> driver. no functional changes are intended.
> 
> I have tested this on my Khadas VIM2 (GXM SoC, with RGMII PHY) and my
> Endless Mini (EC-100, Meson8b SoC with RMII PHY, .dts support is not part
> of mainline yet). no problems were found.
> 
> 
> [0] http://lists.infradead.org/pipermail/linux-amlogic/2018-January/006143.html

Series applied, thank you very much.

  parent reply	other threads:[~2018-02-19 16:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-17 14:08 [net-next PATCH v1 0/3] dwmac-meson8b: small cleanup Martin Blumenstingl
2018-02-17 14:08 ` Martin Blumenstingl
2018-02-17 14:08 ` [net-next PATCH v1 1/3] net: stmmac: dwmac-meson8b: simplify clock registration Martin Blumenstingl
2018-02-17 14:08   ` Martin Blumenstingl
2018-02-17 16:38   ` Jerome Brunet
2018-02-17 16:38     ` Jerome Brunet
2018-02-17 14:08 ` [net-next PATCH v1 2/3] net: stmmac: dwmac-meson8b: only keep struct device around Martin Blumenstingl
2018-02-17 14:08   ` Martin Blumenstingl
2018-02-17 14:08 ` [net-next PATCH v1 3/3] net: stmmac: dwmac-meson8b: make the clock configurations private Martin Blumenstingl
2018-02-17 14:08   ` Martin Blumenstingl
2018-02-17 16:41   ` Jerome Brunet
2018-02-17 16:41     ` Jerome Brunet
2018-02-17 17:42     ` Martin Blumenstingl
2018-02-17 17:42       ` Martin Blumenstingl
2018-02-19 16:27 ` David Miller [this message]
2018-02-19 16:27   ` [net-next PATCH v1 0/3] dwmac-meson8b: small cleanup David Miller

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=20180219.112700.346909623772944138.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=carlo@caione.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=narmstrong@baylibre.com \
    --cc=netdev@vger.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.