From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Danny Kukawka <danny.kukawka@bisect.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Danny Kukawka <dkukawka@suse.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Bruce Allan <bruce.w.allan@intel.com>,
Carolyn Wyborny <carolyn.wyborny@intel.com>,
Don Skidmore <donald.c.skidmore@intel.com>,
Greg Rose <gregory.v.rose@intel.com>,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
Alex Duyck <alexander.h.duyck@intel.com>,
John Ronciak <john.ronciak@intel.com>,
Mitch Williams <mitch.a.williams@intel.com>,
Jiri Pirko <jpirko@redhat.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
e1000-devel@lists.sourceforge.net,
Neil Horman <nhorman@tuxdriver.com>,
Randy Dunlap <rdunlap@xenotime.net>,
Stephen Hemminger <shemminger@vyatta.com>
Subject: Re: [PATCH v2 0/2] Part 1: handle addr_assign_type for random addresses
Date: Thu, 09 Feb 2012 12:09:24 -0800 [thread overview]
Message-ID: <1328818164.3639.15.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1328816934-11508-1-git-send-email-danny.kukawka@bisect.de>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
On Thu, 2012-02-09 at 20:48 +0100, Danny Kukawka wrote:
> This is an updated and split up version of my patch series to
> fix the handling of addr_assign_type for random MAC addresses.
>
> The first part contains the basic changes in etherdevice.h
> and eth.c incl. needed adaptations in the existing code
>
> Danny Kukawka (2):
> eth: reset addr_assign_type if eth_mac_addr() called
> rename dev_hw_addr_random and remove redundant second
>
> drivers/net/ethernet/intel/igbvf/netdev.c | 11 +++++---
> drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 28 ++++++++++++--------
> include/linux/etherdevice.h | 13 +++++----
> net/ethernet/eth.c | 2 +
> 4 files changed, 33 insertions(+), 21 deletions(-)
>
Thanks Danny, I will add both patches to my queue so that we can
validate the changes for ixgbevf and igbvf.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-09 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 19:48 [PATCH v2 0/2] Part 1: handle addr_assign_type for random addresses Danny Kukawka
2012-02-09 19:48 ` [PATCH v2 1/2] eth: reset addr_assign_type if eth_mac_addr() called Danny Kukawka
2012-02-13 5:50 ` David Miller
2012-02-09 19:48 ` [PATCH 2/2] rename dev_hw_addr_random and remove redundant second Danny Kukawka
2012-02-09 20:11 ` Ben Hutchings
2012-02-13 5:50 ` David Miller
2012-02-09 20:09 ` Jeff Kirsher [this message]
2012-07-02 18:55 ` [PATCH v2 0/2] Part 1: handle addr_assign_type for random addresses Shuah Khan
2012-07-02 19:23 ` Jeff Kirsher
2012-07-02 19:41 ` Shuah Khan
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=1328818164.3639.15.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=danny.kukawka@bisect.de \
--cc=davem@davemloft.net \
--cc=dkukawka@suse.de \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=eric.dumazet@gmail.com \
--cc=gregory.v.rose@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=jpirko@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=rdunlap@xenotime.net \
--cc=shemminger@vyatta.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 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).