linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Andy Green <andy@warmcat.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	nicolas.pitre@linaro.org, s-jan@ti.com, patches@linaro.org,
	tony@atomide.com, rostedt@goodmis.org
Subject: Re: [PATCH 0/3] Add ability to set defaultless network device MAC addresses to deterministic computed locally administered values
Date: Fri, 29 Jun 2012 08:50:28 +0000	[thread overview]
Message-ID: <201206290850.28541.arnd@arndb.de> (raw)
In-Reply-To: <20120629054404.11091.31289.stgit@build.warmcat.com>

On Friday 29 June 2012, Andy Green wrote:
> The following series adds some code to generate legal, locally administered
> MAC addresses from OMAP4 CPU Die ID fuse data, and then adds an api to
> devices.c allowing board files to register device paths for network devices
> that wish to use them.
> 
> On PandaBoard / ES, two devices have no board-level MAC either assigned by
> the manufacturer or stored on the board, the last patch in the series adds
> these device paths and gets them set when the network device is registered.
> 
> The patches are against today's linux-omap.
> 

I had already provided my

Acked-by: Arnd Bergmann <arnd@arndb.de>

when we discussed this last year, and Steven also gave his

Tested-by: Steven Rostedt <rostedt@goodmis.org>

I have one comment to the second patch, which is changed slightly
from the older version.

	Arnd

      parent reply	other threads:[~2012-06-29  8:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29  5:55 [PATCH 0/3] Add ability to set defaultless network device MAC addresses to deterministic computed locally administered values Andy Green
2012-06-29  5:55 ` [PATCH 1/3] OMAP2+: add cpu id register to MAC address helper Andy Green
2012-06-29  9:05   ` Tony Lindgren
2012-06-29  9:13     ` Andy Green
2012-06-29  5:55 ` [PATCH 2/3] OMAP2+ devices add mac address allocation register api Andy Green
2012-06-29  8:51   ` Arnd Bergmann
2012-06-29  9:03     ` Andy Green
2012-06-29  9:40   ` Tony Lindgren
2012-06-29 10:07     ` Andy Green
2012-06-29 12:03       ` Tony Lindgren
2012-06-29 13:45         ` Arnd Bergmann
2012-06-29 13:55           ` Tony Lindgren
2012-06-29 13:59             ` Andy Green
2012-06-29 14:33             ` Arnd Bergmann
2012-06-29 14:52               ` Tony Lindgren
2012-06-29 15:05                 ` Arnd Bergmann
2012-07-01  8:58                   ` Tony Lindgren
2012-07-02  7:15                     ` Arnd Bergmann
2012-07-02 10:51                       ` Tony Lindgren
2012-06-29 14:03           ` Andy Green
2012-06-29 14:38             ` Arnd Bergmann
2012-06-29  5:55 ` [PATCH 3/3] OMAP4 PANDA register ethernet and wlan for automatic mac allocation Andy Green
2012-06-29 11:55   ` Tony Lindgren
2012-06-29  8:50 ` Arnd Bergmann [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=201206290850.28541.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=andy@warmcat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nicolas.pitre@linaro.org \
    --cc=patches@linaro.org \
    --cc=rostedt@goodmis.org \
    --cc=s-jan@ti.com \
    --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).