linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Li Yang <leoyang.li@nxp.com>,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 0/2] arm64: dts: freescale: sl28: fix RGMII
Date: Sun, 23 May 2021 13:08:08 +0800	[thread overview]
Message-ID: <20210523050807.GV8194@dragon> (raw)
In-Reply-To: <20210514185553.10095-1-michael@walle.cc>

On Fri, May 14, 2021 at 08:55:51PM +0200, Michael Walle wrote:
> This fixes the RGMII on the sl28 boards. While the network port was
> actually working it is still out-of-spec.
> 
> Please note, that this is split into two patches because each one fixes
> a different commit.
> 
> Changes since v1:
>   - use different subjects for the two patches. I didn't use sl28-varN
> 	because I'd like to keep "sl28:" for all the sl28 related patches.
> 
> Michael Walle (2):
>   arm64: dts: freescale: sl28: var4: fix RGMII clock and voltage
>   arm64: dts: freescale: sl28: var1: fix RGMII clock and voltage

Applied both, thanks.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2021-05-23  5:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 18:55 [PATCH v2 0/2] arm64: dts: freescale: sl28: fix RGMII Michael Walle
2021-05-14 18:55 ` [PATCH v2 1/2] arm64: dts: freescale: sl28: var4: fix RGMII clock and voltage Michael Walle
2021-05-14 18:55 ` [PATCH v2 2/2] arm64: dts: freescale: sl28: var1: " Michael Walle
2021-05-23  5:08 ` Shawn Guo [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=20210523050807.GV8194@dragon \
    --to=shawnguo@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --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 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).