From: David Miller <davem@davemloft.net>
To: sassmann@redhat.com
Cc: netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net,
jeffrey.t.kirsher@intel.com, gregory.v.rose@intel.com
Subject: Re: [net-next-2.6 PATCH] igbvf, ixgbevf: use dev_hw_addr_random
Date: Tue, 27 Jul 2010 13:18:36 -0700 (PDT) [thread overview]
Message-ID: <20100727.131836.232892891.davem@davemloft.net> (raw)
In-Reply-To: <4C4EA5E2.1050909@redhat.com>
From: Stefan Assmann <sassmann@redhat.com>
Date: Tue, 27 Jul 2010 11:24:50 +0200
> From: Stefan Assmann <sassmann@redhat.com>
>
> Both igbvf and ixgbevf should set addr_assign_type to NET_ADDR_RANDOM
> so udev creates persistent net rules by matching the device path.
> Do this by using the dev_hw_addr_random helper function.
>
> Signed-off-by: Stefan Assmann <sassmann@redhat.com>
Applied.
prev parent reply other threads:[~2010-07-27 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 9:24 [net-next-2.6 PATCH] igbvf, ixgbevf: use dev_hw_addr_random Stefan Assmann
2010-07-27 20:18 ` David Miller [this message]
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=20100727.131836.232892891.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.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).