From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: shuah.khan@hp.com
Cc: Danny Kukawka <danny.kukawka@bisect.de>,
"David S. Miller" <davem@davemloft.net>,
Danny Kukawka <dkukawka@suse.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Part 1: handle addr_assign_type for random addresses
Date: Mon, 02 Jul 2012 12:23:32 -0700 [thread overview]
Message-ID: <1341257012.1987.2.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1341255355.2750.23.camel@lorien2>
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
On Mon, 2012-07-02 at 12:55 -0600, Shuah Khan wrote:
> On Thu, 2012-02-09 at 12:09 -0800, Jeff Kirsher wrote:
>
> >
> > Thanks Danny, I will add both patches to my queue so that we can
> > validate the changes for ixgbevf and igbvf.
>
> Jeff,
>
> Which upstream kernel did this patch end up in? Also did it make it into
> any of the stable releases?
>
> Thanks,
> -- Shuah
>
It looks like it was accepted into kernel 3.3. I am not aware of any
stable kernels earlier than 3.3 that picked up the patch.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-02 19:23 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 ` [PATCH v2 0/2] Part 1: handle addr_assign_type for random addresses Jeff Kirsher
2012-07-02 18:55 ` Shuah Khan
2012-07-02 19:23 ` Jeff Kirsher [this message]
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=1341257012.1987.2.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=danny.kukawka@bisect.de \
--cc=davem@davemloft.net \
--cc=dkukawka@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah.khan@hp.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).