From: Pavel Emelyanov <xemul@openvz.org>
To: Patrick McHardy <kaber@trash.net>,
"David S. Miller" <davem@davemloft.net>
Cc: Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [VLAN]: Correctly handle device notifications for layered VLAN devices
Date: Tue, 20 May 2008 17:25:47 +0400 [thread overview]
Message-ID: <4832D15B.3070003@openvz.org> (raw)
In-Reply-To: <4832D0D6.3020503@trash.net>
Patrick McHardy wrote:
> commit cf794e6af782a838252dfc9fc6f10f7a7f66f62a
> Author: Patrick McHardy <kaber@trash.net>
> Date: Tue May 20 15:12:49 2008 +0200
>
> [VLAN]: Correctly handle device notifications for layered VLAN devices
>
> Commit 30688a9 ([VLAN]: Handle vlan devices net namespace changing)
> changed the device notifier to special-case notifications for VLAN
> devices, effectively disabling state propagation to underlying VLAN
> devices. This is needed for layered VLANs though, so restore the
> original behaviour.
>
> Signed-off-by: Patrick McHardy <kaber@trash.net>
Acked-by: Pavel Emelyanov <xemul@openvz.org>
next prev parent reply other threads:[~2008-05-20 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 13:23 [VLAN]: Correctly handle device notifications for layered VLAN devices Patrick McHardy
2008-05-20 13:25 ` Pavel Emelyanov [this message]
2008-05-20 21:38 ` 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=4832D15B.3070003@openvz.org \
--to=xemul@openvz.org \
--cc=davem@davemloft.net \
--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 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.