netdev - Re: [PATCH v2 2/2] adi: adapt to eth_hw_addr_random() and changes in arch/blackfin

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201202181428.07491.danny.kukawka@bisect.de>
Date:	Sat, 18 Feb 2012 14:28:06 +0100
From:	Danny Kukawka <danny.kukawka@...ect.de>
To:	Joe Perches <joe@...ches.com>
Cc:	Mike Frysinger <vapier@...too.org>,
	"David S. Miller" <davem@...emloft.net>,
	Sonic Zhang <sonic.zhang@...log.com>,
	Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
	Bob Liu <bob.liu@...log.com>,
	uclinux-dist-devel@...ckfin.uclinux.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] adi: adapt to eth_hw_addr_random() and changes in arch/blackfin

On Samstag, 18. Februar 2012, Joe Perches wrote:
> 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.

Okay ... I'll send a patch to print a message via netdev_info from 
eth_hw_addr_random() and to cleanup the drivers.

Danny

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html