From: Tony Lindgren <tony@atomide.com>
To: Mugunthan V N <mugunthanvnm@ti.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
alex.aring@gmail.com
Subject: Re: [net-next PATCH 3/3] ARM: dts: am33xx: update cpsw compatible
Date: Thu, 13 Aug 2015 02:56:14 -0700 [thread overview]
Message-ID: <20150813095613.GC4215@atomide.com> (raw)
In-Reply-To: <1439373175-8650-4-git-send-email-mugunthanvnm@ti.com>
* Mugunthan V N <mugunthanvnm@ti.com> [150812 02:56]:
> CPSW driver has been updated with compatibles for enabling errata
> workarounds. So updating cpsw compatibles.
>
> Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
This too:
Acked-by: Tony Lindgren <tony@atomide.com>
> ---
> arch/arm/boot/dts/am33xx.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
> index 21fcc44..8b59c86 100644
> --- a/arch/arm/boot/dts/am33xx.dtsi
> +++ b/arch/arm/boot/dts/am33xx.dtsi
> @@ -700,7 +700,7 @@
> };
>
> mac: ethernet@4a100000 {
> - compatible = "ti,cpsw";
> + compatible = "ti,am335x-cpsw","ti,cpsw";
> ti,hwmods = "cpgmac0";
> clocks = <&cpsw_125mhz_gclk>, <&cpsw_cpts_rft_clk>;
> clock-names = "fck", "cpts";
> --
> 2.5.0.234.gefc8a62
>
next prev parent reply other threads:[~2015-08-13 9:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 9:52 [net-next PATCH 0/3] Add AM335x PG1.0 CPSW errata workaround Mugunthan V N
2015-08-12 9:52 ` [net-next PATCH 1/3] drivers: net: cpsw: add am335x errata workarround for interrutps Mugunthan V N
2015-08-24 10:04 ` Sekhar Nori
2015-08-25 6:17 ` Mugunthan V N
2015-08-12 9:52 ` [net-next PATCH 2/3] ARM: dts: dra7: update cpsw compatible Mugunthan V N
2015-08-13 9:55 ` Tony Lindgren
2015-08-12 9:52 ` [net-next PATCH 3/3] ARM: dts: am33xx: " Mugunthan V N
2015-08-13 9:56 ` Tony Lindgren [this message]
2015-08-13 23:51 ` [net-next PATCH 0/3] Add AM335x PG1.0 CPSW errata workaround 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=20150813095613.GC4215@atomide.com \
--to=tony@atomide.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.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 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).