From: Patrick McHardy <kaber@trash.net>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
devel@openvz.org
Subject: Re: [PATCH][VLAN]: Proc entry is not renamed when vlan device name changes.
Date: Tue, 01 Apr 2008 08:53:12 +0200 [thread overview]
Message-ID: <47F1DBD8.9080603@trash.net> (raw)
In-Reply-To: <47F0E1C7.7040908@openvz.org>
Pavel Emelyanov wrote:
> This may lead to situations, when each of two proc entries produce
> data for the other's device.
>
> Looks like a BUG, so this patch is for net-2.6. It will not apply
> to net-2.6.26 since dev->nd_net access is replaced with dev_net(dev)
> one. Should I rework the patch to fit 2.6.26?
No, since its a bugfix it should go in net-2.6. Dave, please apply.
next prev parent reply other threads:[~2008-04-01 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 13:06 [PATCH][VLAN]: Proc entry is not renamed when vlan device name changes Pavel Emelyanov
2008-04-01 6:53 ` Patrick McHardy [this message]
2008-04-02 7:08 ` 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=47F1DBD8.9080603@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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).