All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: martin.blumenstingl@googlemail.com
Cc: netdev@vger.kernel.org, linux-amlogic@lists.infradead.org,
	robh+dt@kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] prepare dwmac-meson8b for G12A specific initialization
Date: Mon, 22 Jun 2020 16:24:29 -0700 (PDT)	[thread overview]
Message-ID: <20200622.162429.585862651883881701.davem@davemloft.net> (raw)
In-Reply-To: <20200620192641.175754-1-martin.blumenstingl@googlemail.com>

From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Date: Sat, 20 Jun 2020 21:26:39 +0200

> Some users are reporting that RGMII (and sometimes also RMII) Ethernet
> is not working for them on G12A/G12B/SM1 boards. Upon closer inspection
> of the vendor code for these SoCs new register bits are found.
> 
> It's not clear yet how these registers work. Add a new compatible string
> as the first preparation step to improve Ethernet support on these SoCs.

Series applied to net-next, thanks Martin.

  parent reply	other threads:[~2020-06-22 23:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-20 19:26 [PATCH 0/2] prepare dwmac-meson8b for G12A specific initialization Martin Blumenstingl
2020-06-20 19:26 ` Martin Blumenstingl
2020-06-20 19:26 ` Martin Blumenstingl
2020-06-20 19:26 ` [PATCH 1/2] dt-bindings: net: dwmac-meson: Add a compatible string for G12A onwards Martin Blumenstingl
2020-06-20 19:26   ` Martin Blumenstingl
2020-06-20 19:26   ` Martin Blumenstingl
2020-06-20 19:26 ` [PATCH 2/2] net: stmmac: dwmac-meson8b: add a compatible string for G12A SoCs Martin Blumenstingl
2020-06-20 19:26   ` Martin Blumenstingl
2020-06-20 19:26   ` Martin Blumenstingl
2020-06-22 23:24 ` David Miller [this message]
2020-08-17 17:48 ` [PATCH 0/2] prepare dwmac-meson8b for G12A specific initialization patchwork-bot+linux-amlogic

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=20200622.162429.585862651883881701.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@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.