netdev - Re: [PATCH v2] net: Add eth_platform_get_mac

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: <3EF5B56E-FA0D-4A4F-A6C6-DE306FA1E610@intel.com>
Date:	Wed, 13 Jan 2016 00:59:00 +0000
From:	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
To:	Sowmini Varadhan <sowmini.varadhan@...cle.com>
CC:	David Miller <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH v2] net: Add eth_platform_get_mac_address() helper.


> On Jan 12, 2016, at 16:49, Sowmini Varadhan <sowmini.varadhan@...cle.com> wrote:
> 
>> On (01/06/16 16:33), David Miller wrote:
>> 
>> A repeating pattern in drivers has become to use OF node information
>> and, if not found, platform specific host information to extract the
>> ethernet address for a given device.
>    :
>> Consolidate this into a portable routine, and provide the
>> arch_get_platform_mac_address() weak function hook for all
>> architectures to implement if they want.
>    :
>> As promised back in November, I'm commiting this into net-next
>> now.  I'd work on the conversions of existing drivers, but I'd
>> rather someone with access to the hardware to so.
> 
> I finally have all the ducks lined up for ixgbe/i40e around this. 
> Should I go ahead and send this off (I think it first gets staged 
> through Jeff's repo?) or is it better to wait for net-next to be 
> open again?

please go ahead and send it to intel-wired-lan@...ts.osuosl.org so we can review and test the driver parts so when net-next opens it should be ready to push upstream.