From: Sekhar Nori <nsekhar@ti.com>
To: Mugunthan V N <mugunthanvnm@ti.com>, <netdev@vger.kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-omap@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Tony Lindgren <tony@atomide.com>, <alex.aring@gmail.com>
Subject: Re: [net-next PATCH 1/3] drivers: net: cpsw: add am335x errata workarround for interrutps
Date: Mon, 24 Aug 2015 15:34:24 +0530 [thread overview]
Message-ID: <55DAEC28.3030107@ti.com> (raw)
In-Reply-To: <1439373175-8650-2-git-send-email-mugunthanvnm@ti.com>
Hi Mugunthan,
On Wednesday 12 August 2015 03:22 PM, Mugunthan V N wrote:
> +static const struct of_device_id cpsw_of_mtable[] = {
> + { .compatible = "ti,cpsw", .data = &cpsw_devtype[CPSW], },
> + { .compatible = "ti,am335x-cpsw", .data = &cpsw_devtype[AM335X_CPSW], },
> + { .compatible = "ti,am4372-cpsw", .data = &cpsw_devtype[AM4372_CPSW], },
> + { .compatible = "ti,dra7-cpsw", .data = &cpsw_devtype[DRA7_CPSW], },
I do not see documentation added for these compatibles. Since the series
is already applied, can you send additional patches adding documentation?
Thanks,
Sekhar
next prev parent reply other threads:[~2015-08-24 10:04 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 [this message]
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
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=55DAEC28.3030107@ti.com \
--to=nsekhar@ti.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 \
--cc=tony@atomide.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).