From: Joe Perches <joe@perches.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Danny Kukawka <danny.kukawka@bisect.de>,
"David S. Miller" <davem@davemloft.net>,
Sonic Zhang <sonic.zhang@analog.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Bob Liu <bob.liu@analog.com>,
uclinux-dist-devel@blackfin.uclinux.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] adi: adapt to eth_hw_addr_random() and changes in arch/blackfin
Date: Fri, 17 Feb 2012 15:27:43 -0800 [thread overview]
Message-ID: <1329521263.584.50.camel@joe2Laptop> (raw)
In-Reply-To: <201202171815.59846.vapier@gentoo.org>
On Fri, 2012-02-17 at 18:15 -0500, Mike Frysinger wrote:
> On Friday 17 February 2012 05:57:54 Danny Kukawka wrote:
> > Maybe. Many drivers already print information about setting a random mac
> > address to a netdevice. Some with printk, some via
> > netdev_warn/netdev_info/netdev_dbg or netif_dbg and other with costum
> > methods. I could unify this, in a next step with a netdev_info in
> > eth_hw_addr_random(), if it's okay for David.
> i think unification in the core makes sense. it enforces consistency and
> removes duplication.
It's a good idea.
next prev parent reply other threads:[~2012-02-17 23:27 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
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 [this message]
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=1329521263.584.50.camel@joe2Laptop \
--to=joe@perches.com \
--cc=bob.liu@analog.com \
--cc=danny.kukawka@bisect.de \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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