devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mugunthan V N <mugunthanvnm@ti.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: netdev@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	benoit.cousson@linaro.org, linux-omap@vger.kernel.org,
	davem@davemloft.net
Subject: Re: [net-next PATCH v4 0/5] Adding pinctrl PM support for CPSW and MDIO
Date: Thu, 6 Jun 2013 13:57:25 +0530	[thread overview]
Message-ID: <51B047ED.5060203@ti.com> (raw)
In-Reply-To: <51B03D4E.3090504@ti.com>

On 6/6/2013 1:12 PM, Benoit Cousson wrote:
> Hi Mugunthan,
>
> On 06/05/2013 07:08 PM, Mugunthan V N wrote:
>> This patch series adds the following features
>> * Adding pinctrl PM support for CPSW and MDIO for Power Optimization
>> * Adding phy address to the CPSW node for EVMsk board
>>
>> Changes from initial version
>> * Fixed the multiline function call indentation as per David Miller
>>    recommendation.
>>
>> Changes from v2
>> * Fixed the multi comment style as per net coding style
>> * Fixed checkpatch error (more than 80 characters)
>>
>> Changes from v3
>> * Removed below patch as it has already merged to net-next
>> 	ARM: dts: AM33XX: Add CPSW phy_id device tree data to am335x-evmsk
>> * Rebased to net-next as there was a merge conflict in DT files
> You should try to avoid pushing DTS patches outside the arm-soc tree, it
> will generate a bunch a conflict when arm-soc and net trees will be merged.
>
> Could you post separately all the DTS patches and rebase them on the
> for_3.11/dts branch that already contains a bunch of AM33xx patches?
Benoit

Will separate out the DT patches and will submit on top of for_3.11/dts 
today as v5.

Regards
Mugunthan V N

      reply	other threads:[~2013-06-06  8:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 17:08 [net-next PATCH v4 0/5] Adding pinctrl PM support for CPSW and MDIO Mugunthan V N
2013-06-05 17:08 ` [net-next PATCH v4 1/5] net: cpsw: enhance pinctrl support Mugunthan V N
     [not found]   ` <1370452099-24026-2-git-send-email-mugunthanvnm-l0cyMroinI0@public.gmane.org>
2013-06-05 19:23     ` Mark Brown
2013-06-06  5:59       ` Mugunthan V N
2013-06-06  8:50         ` Mark Brown
2013-06-07  7:31           ` Linus Walleij
2013-06-07  7:42             ` David Miller
2013-06-07 14:49               ` Mugunthan V N
2013-06-10 15:48                 ` Linus Walleij
2013-06-13  9:54                   ` David Miller
2013-06-05 17:08 ` [net-next PATCH v4 2/5] net: davinci_mdio: " Mugunthan V N
2013-06-05 17:08 ` [net-next PATCH v4 3/5] ARM: dts: AM33XX: Add pinmux configuration for CPSW to beaglebone Mugunthan V N
2013-06-06  7:06   ` Florian Vaussard
     [not found]     ` <51B034ED.7040603-p8DiymsW2f8@public.gmane.org>
2013-06-06  8:21       ` Mugunthan V N
2013-06-05 17:08 ` [net-next PATCH v4 4/5] ARM: dts: AM33XX: Add pinmux configuration for CPSW to EVMsk Mugunthan V N
2013-06-05 17:08 ` [net-next PATCH v4 5/5] ARM: dts: AM33XX: Add pinmux configuration for CPSW to am335x EVM Mugunthan V N
2013-06-06  7:42 ` [net-next PATCH v4 0/5] Adding pinctrl PM support for CPSW and MDIO Benoit Cousson
2013-06-06  8:27   ` 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=51B047ED.5060203@ti.com \
    --to=mugunthanvnm@ti.com \
    --cc=b-cousson@ti.com \
    --cc=benoit.cousson@linaro.org \
    --cc=davem@davemloft.net \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-omap@vger.kernel.org \
    --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).