From: David Miller <davem@davemloft.net>
To: vfalico@gmail.com
Cc: netdev@vger.kernel.org, j.vosburgh@gmail.com, andy@greyhouse.net
Subject: Re: [PATCH net-next] bonding: make it possible to have unlimited nested upper vlans
Date: Sun, 20 Jul 2014 20:35:24 -0700 (PDT) [thread overview]
Message-ID: <20140720.203524.1312422901001203305.davem@davemloft.net> (raw)
In-Reply-To: <1405609343-3502-1-git-send-email-vfalico@gmail.com>
From: Veaceslav Falico <vfalico@gmail.com>
Date: Thu, 17 Jul 2014 17:02:23 +0200
> Currently we're limited by a constant level of vlan nestings, and fail to
> find anything beyound that level (currently 2).
>
> To fix this - remove the limit of nestings when going through device tree,
> and when the end device is found - allocate the needed amount of vlan tags
> and return them, instead of found/not found.
>
> CC: Jay Vosburgh <j.vosburgh@gmail.com>
> CC: Andy Gospodarek <andy@greyhouse.net>
> Signed-off-by: Veaceslav Falico <vfalico@gmail.com>
Looks good, applied, thanks.
prev parent reply other threads:[~2014-07-21 3:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 15:02 [PATCH net-next] bonding: make it possible to have unlimited nested upper vlans Veaceslav Falico
2014-07-21 3:35 ` 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=20140720.203524.1312422901001203305.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--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).