From: Stephen Hemminger <stephen@networkplumber.org>
To: Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <gospo@cumulusnetworks.com>
Cc: netdev@vger.kernel.org
Subject: Fw: [Bug 89161] Regression in bonding driver with devices that have no MAC address
Date: Wed, 23 Sep 2015 11:00:44 -0700 [thread overview]
Message-ID: <20150923110044.07bda5bb@urahara> (raw)
Begin forwarded message:
Date: Wed, 23 Sep 2015 04:07:34 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 89161] Regression in bonding driver with devices that have no MAC address
https://bugzilla.kernel.org/show_bug.cgi?id=89161
--- Comment #2 from Toby Corkindale <tjc@wintrmute.net> ---
Hi, just checking in to see if anyone's looked at this.. have seen there's been
a bunch of commits to the bonding driver since July 15 but the bit of relevant
code still looks the same.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2015-09-23 18:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150923110044.07bda5bb@urahara \
--to=stephen@networkplumber.org \
--cc=gospo@cumulusnetworks.com \
--cc=j.vosburgh@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.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).