From: Jon Stanley <jstanley@rmrf.net>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, fubar@us.ibm.com,
andy@greyhouse.net, kaber@trash.net
Subject: Re: [patch net] vlan: fix bond/team enslave of vlan challenged slave/port
Date: Mon, 15 Oct 2012 16:38:44 -0400 [thread overview]
Message-ID: <CAJtaB1vRoArmDe_FB_dF-oQUcSsHPbTQ31wzPJLPtLKsq0k53Q@mail.gmail.com> (raw)
In-Reply-To: <CAJtaB1ugcEp13LYX6yJL0DX4EVX53h7MyumzRGDLZ_u8fyu_WA@mail.gmail.com>
On Mon, Oct 15, 2012 at 10:53 AM, Jon Stanley <jstanley@rmrf.net> wrote:
> However, I'm now running into a new issue. Note that I've backported
> this to an older kernel (3.3.2, eww)
My bad, I tried this on mainline and it works fine. Any pointers on
what needs to get backported into 3.3 before I go pulling my hair out
over it? :)
next prev parent reply other threads:[~2012-10-15 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 14:30 [patch net] vlan: fix bond/team enslave of vlan challenged slave/port Jiri Pirko
2012-10-15 14:53 ` Jon Stanley
2012-10-15 20:38 ` Jon Stanley [this message]
2012-10-16 12:59 ` Jiri Pirko
2012-10-16 18:56 ` 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=CAJtaB1vRoArmDe_FB_dF-oQUcSsHPbTQ31wzPJLPtLKsq0k53Q@mail.gmail.com \
--to=jstanley@rmrf.net \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=jiri@resnulli.us \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/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).