From: Mugunthan V N <mugunthanvnm@ti.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-omap@vger.kernel.org, b-cousson@ti.com, paul@pwsan.com
Subject: Re: [net-next PATCH 0/6] Adding pinctrl PM support for CPSW and Davinci MDIO drivers
Date: Fri, 3 May 2013 15:19:42 +0530 [thread overview]
Message-ID: <51838836.8050104@ti.com> (raw)
In-Reply-To: <20130503.034252.972676071176953465.davem@davemloft.net>
On 5/3/2013 1:12 PM, David Miller wrote:
> Please read:
>
> http://marc.info/?l=linux-netdev&m=136730964130303&w=2
Sorry, will resend the patch series one net is merged with net-next.
Regards
Mugunthan V N
prev parent reply other threads:[~2013-05-03 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 7:38 [net-next PATCH 0/6] Adding pinctrl PM support for CPSW and Davinci MDIO drivers Mugunthan V N
2013-05-03 7:38 ` [net-next PATCH 1/6] net: cpsw: enhance pinctrl support Mugunthan V N
2013-05-03 7:38 ` [net-next PATCH 2/6] net: davinci_mdio: " Mugunthan V N
2013-05-03 7:38 ` [net-next PATCH 3/6] ARM: dts: AM33XX: Add pinmux configuration for CPSW to beaglebone Mugunthan V N
2013-05-03 7:38 ` [net-next PATCH 4/6] ARM: dts: AM33XX: Add CPSW phy_id device tree data to am335x-evmsk Mugunthan V N
2013-05-03 7:38 ` [net-next PATCH 5/6] ARM: dts: AM33XX: Add pinmux configuration for CPSW to EVMsk Mugunthan V N
2013-05-03 7:38 ` [net-next PATCH 6/6] ARM: dts: AM33XX: Add pinmux configuration for CPSW to am335x EVM Mugunthan V N
2013-05-03 7:42 ` [net-next PATCH 0/6] Adding pinctrl PM support for CPSW and Davinci MDIO drivers David Miller
2013-05-03 9:49 ` Mugunthan V N [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=51838836.8050104@ti.com \
--to=mugunthanvnm@ti.com \
--cc=b-cousson@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@pwsan.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).