From: Vlad Yasevich <vyasevic@redhat.com>
To: netdev@vger.kernel.org
Cc: shemminger@vyatta.com, bridge@lists.linux-foundation.org
Subject: Re: [Bridge] [PATCH 0/2] bridge: Fix forwarding of 8021AD frames
Date: Wed, 26 Mar 2014 12:09:52 -0400 [thread overview]
Message-ID: <5332FBD0.2010802@redhat.com> (raw)
In-Reply-To: <1395849627-15711-1-git-send-email-vyasevic@redhat.com>
On 03/26/2014 12:00 PM, Vlad Yasevich wrote:
> Bridge has its own way to deterine if the packet is forwardable and it doesn't
> support 8021ad tags correctly. Instead just allow bridge to use an
> existing is_skb_forwardable() function.
>
>
> Vlad Yasevich (2):
> net: Allow modules to use is_skb_forwardable
> bridge: use is_skb_forwardable in forward path
>
> include/linux/netdevice.h | 1 +
> net/bridge/br_forward.c | 7 +------
> net/core/dev.c | 3 ++-
> 3 files changed, 4 insertions(+), 7 deletions(-)
>
Self-nack. Missed one of the hunks in patch2.
-vlad
WARNING: multiple messages have this Message-ID (diff)
From: Vlad Yasevich <vyasevic@redhat.com>
To: netdev@vger.kernel.org
Cc: bridge@lists.linux-foundation.org, shemminger@vyatta.com
Subject: Re: [PATCH 0/2] bridge: Fix forwarding of 8021AD frames
Date: Wed, 26 Mar 2014 12:09:52 -0400 [thread overview]
Message-ID: <5332FBD0.2010802@redhat.com> (raw)
In-Reply-To: <1395849627-15711-1-git-send-email-vyasevic@redhat.com>
On 03/26/2014 12:00 PM, Vlad Yasevich wrote:
> Bridge has its own way to deterine if the packet is forwardable and it doesn't
> support 8021ad tags correctly. Instead just allow bridge to use an
> existing is_skb_forwardable() function.
>
>
> Vlad Yasevich (2):
> net: Allow modules to use is_skb_forwardable
> bridge: use is_skb_forwardable in forward path
>
> include/linux/netdevice.h | 1 +
> net/bridge/br_forward.c | 7 +------
> net/core/dev.c | 3 ++-
> 3 files changed, 4 insertions(+), 7 deletions(-)
>
Self-nack. Missed one of the hunks in patch2.
-vlad
next prev parent reply other threads:[~2014-03-26 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 16:00 [Bridge] [PATCH 0/2] bridge: Fix forwarding of 8021AD frames Vlad Yasevich
2014-03-26 16:00 ` Vlad Yasevich
2014-03-26 16:00 ` [Bridge] " Vlad Yasevich
2014-03-26 16:00 ` Vlad Yasevich
2014-03-26 16:00 ` [Bridge] [PATCH 1/2] net: Allow modules to use is_skb_forwardable Vlad Yasevich
2014-03-26 16:00 ` Vlad Yasevich
2014-03-26 21:35 ` [Bridge] " Stephen Hemminger
2014-03-26 21:35 ` Stephen Hemminger
2014-03-27 0:50 ` [Bridge] " Vlad Yasevich
2014-03-27 0:50 ` Vlad Yasevich
2014-03-26 16:00 ` [Bridge] [PATCH 2/2] bridge: use is_skb_forwardable in forward path Vlad Yasevich
2014-03-26 16:00 ` Vlad Yasevich
2014-03-26 16:09 ` Vlad Yasevich [this message]
2014-03-26 16:09 ` [PATCH 0/2] bridge: Fix forwarding of 8021AD frames Vlad Yasevich
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=5332FBD0.2010802@redhat.com \
--to=vyasevic@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.