From: David Miller <davem@davemloft.net>
To: vapier@gentoo.org
Cc: danny.kukawka@bisect.de, linux-kernel@vger.kernel.org,
dkukawka@suse.de, uclinux-dist-devel@blackfin.uclinux.org,
lliubbo@gmail.com, sonic.zhang@analog.com,
paul.gortmaker@windriver.com, realmz6@gmail.com, lars@metafoo.de,
scott.jiang@analog.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 1/2] arch/blackfin: don't generate random mac in bfin_get_ether_addr()
Date: Sun, 19 Feb 2012 19:05:19 -0500 (EST) [thread overview]
Message-ID: <20120219.190519.2247992297753168519.davem@davemloft.net> (raw)
In-Reply-To: <CAMjpGUdJjG3OExzHWd8+FwWsG-vCsL-NVe=ivS5VeeV6G0-_Tw@mail.gmail.com>
From: Mike Frysinger <vapier@gentoo.org>
Date: Thu, 16 Feb 2012 23:38:11 -0500
> On Thu, Feb 16, 2012 at 12:09, Danny Kukawka wrote:
>> Changed bfin_get_ether_addr() to return a state and to
>> set no random mac address if the board don't provide one.
>>
>> Let the caller of bfin_get_ether_addr() set a random mac
>> address if the return value is not 0.
>
> Acked-by: Mike Frysinger <vapier@gentoo.org>
Applied.
next prev parent reply other threads:[~2012-02-20 0:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 17:09 [PATCH v2 0/2] Part 3: handle random addresses on blackfin Danny Kukawka
2012-02-16 17:09 ` [PATCH v2 1/2] arch/blackfin: don't generate random mac in bfin_get_ether_addr() Danny Kukawka
2012-02-17 4:38 ` Mike Frysinger
2012-02-20 0:05 ` David Miller [this message]
2012-02-16 17:09 ` [PATCH v2 2/2] adi: adapt to eth_hw_addr_random() and changes in arch/blackfin Danny Kukawka
2012-02-17 4:37 ` Mike Frysinger
2012-02-17 10:57 ` Danny Kukawka
2012-02-17 23:15 ` Mike Frysinger
2012-02-17 23:27 ` Joe Perches
2012-02-18 13:28 ` Danny Kukawka
2012-02-19 2:47 ` Mike Frysinger
2012-02-20 0:05 ` David Miller
2012-02-20 0:05 ` 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=20120219.190519.2247992297753168519.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=danny.kukawka@bisect.de \
--cc=dkukawka@suse.de \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lliubbo@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=realmz6@gmail.com \
--cc=scott.jiang@analog.com \
--cc=sonic.zhang@analog.com \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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).