netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mugunthan V N <mugunthanvnm@ti.com>
To: Markus Pargmann <mpa@pengutronix.de>,
	"David S. Miller" <davem@davemloft.net>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Wolfram Sang" <wsa@the-dreams.de>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	kernel@pengutronix.de
Subject: Re: [PATCH RESEND v6 0/7] net: cpsw: Support for am335x chip MACIDs
Date: Mon, 29 Sep 2014 14:21:28 +0530	[thread overview]
Message-ID: <54291D90.4010806@ti.com> (raw)
In-Reply-To: <1411973599-18908-1-git-send-email-mpa@pengutronix.de>

On Monday 29 September 2014 12:23 PM, Markus Pargmann wrote:
> Hi,
> 
> Another resend of this series to add the netdev list.
> 
> This series adds support to the cpsw driver to read the MACIDs of the am335x
> chip and use them as fallback. These addresses are only used if there are no
> mac addresses in the devicetree, for example set by a bootloader.
> 
> Best regards,
> 
> Markus
> 
> 
> Markus Pargmann (7):
>   DT doc: net: cpsw mac-address is optional
>   net: cpsw: Add missing return value
>   net: cpsw: header, Add missing include
>   net: cpsw: Replace pr_err by dev_err
>   net: cpsw: Add am33xx MACID readout
>   am33xx: define syscon control module device node
>   arm: dts: am33xx, Add syscon phandle to cpsw node
> 
>  Documentation/devicetree/bindings/net/cpsw.txt |  6 +++-
>  arch/arm/boot/dts/am33xx.dtsi                  |  6 ++++
>  drivers/net/ethernet/ti/Kconfig                |  2 ++
>  drivers/net/ethernet/ti/cpsw.c                 | 45 ++++++++++++++++++++++++--
>  drivers/net/ethernet/ti/cpsw.h                 |  1 +
>  5 files changed, 57 insertions(+), 3 deletions(-)
> 

Acked-by: Mugunthan V N <mugunthanvnm@gmail.com>

Regards
Mugunthan V N

  parent reply	other threads:[~2014-09-29  8:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29  6:53 [PATCH RESEND v6 0/7] net: cpsw: Support for am335x chip MACIDs Markus Pargmann
2014-09-29  6:53 ` [PATCH RESEND v6 1/7] DT doc: net: cpsw mac-address is optional Markus Pargmann
2014-09-29  6:53 ` [PATCH RESEND v6 2/7] net: cpsw: Add missing return value Markus Pargmann
2014-09-29  6:53 ` [PATCH RESEND v6 3/7] net: cpsw: header, Add missing include Markus Pargmann
2014-09-29  6:53 ` [PATCH RESEND v6 4/7] net: cpsw: Replace pr_err by dev_err Markus Pargmann
     [not found] ` <1411973599-18908-1-git-send-email-mpa-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2014-09-29  6:53   ` [PATCH RESEND v6 5/7] net: cpsw: Add am33xx MACID readout Markus Pargmann
2014-09-29  6:53 ` [PATCH RESEND v6 6/7] am33xx: define syscon control module device node Markus Pargmann
2014-09-29  6:53 ` [PATCH RESEND v6 7/7] arm: dts: am33xx, Add syscon phandle to cpsw node Markus Pargmann
2014-09-29  8:51 ` Mugunthan V N [this message]
2014-09-30  5:31 ` [PATCH RESEND v6 0/7] net: cpsw: Support for am335x chip MACIDs 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=54291D90.4010806@ti.com \
    --to=mugunthanvnm@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mpa@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tony@atomide.com \
    --cc=wsa@the-dreams.de \
    /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).