From: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v2] net: Add eth_platform_get_mac_address() helper.
Date: Wed, 13 Jan 2016 00:59:00 +0000 [thread overview]
Message-ID: <3EF5B56E-FA0D-4A4F-A6C6-DE306FA1E610@intel.com> (raw)
In-Reply-To: <20160113004916.GA28880@oracle.com>
> On Jan 12, 2016, at 16:49, Sowmini Varadhan <sowmini.varadhan@oracle.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@lists.osuosl.org so we can review and test the driver parts so when net-next opens it should be ready to push upstream.
next prev parent reply other threads:[~2016-01-13 0:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 21:33 [PATCH v2] net: Add eth_platform_get_mac_address() helper David Miller
2016-01-06 21:45 ` Sowmini Varadhan
2016-01-06 23:12 ` Joe Perches
2016-01-06 23:26 ` Bjørn Mork
2016-01-06 23:32 ` Joe Perches
2016-01-06 23:41 ` Bjørn Mork
2016-01-07 0:01 ` David Miller
2016-01-07 0:02 ` Joe Perches
2016-01-13 0:49 ` Sowmini Varadhan
2016-01-13 0:59 ` Kirsher, Jeffrey T [this message]
2016-01-13 2:40 ` 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=3EF5B56E-FA0D-4A4F-A6C6-DE306FA1E610@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.