From: Stephen Hemminger <shemminger@vyatta.com>
To: Wang Chen <wangchen@cn.fujitsu.com>
Cc: "David S. Miller" <davem@davemloft.net>,
NETDEV <netdev@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH net-next 4/8] bridge: sysfs cleanup
Date: Thu, 19 Jun 2008 18:19:45 -0700 [thread overview]
Message-ID: <20080619181945.2b242e4d@extreme> (raw)
In-Reply-To: <485AFFF3.6070802@cn.fujitsu.com>
On Fri, 20 Jun 2008 08:55:15 +0800
Wang Chen <wangchen@cn.fujitsu.com> wrote:
> When I am doing this series of patch, I notice that bridge's sysfs are
> not cleanuped after failure and bridge delete.
>
> Here is the patch for it.
>
> Signed-off-by: Wang Chen <wangchen@cn.fujitsu.com>
Let me look at this, I don't think it used to be a problem before the
conversion from class_device to just device model.
next prev parent reply other threads:[~2008-06-20 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 0:55 [PATCH net-next 4/8] bridge: sysfs cleanup Wang Chen
2008-06-20 1:19 ` Stephen Hemminger [this message]
2008-06-20 2:17 ` Wang Chen
2008-06-20 4:48 ` Wang Chen
2008-06-20 17:44 ` Stephen Hemminger
2008-06-21 3:41 ` Wang Chen
2008-06-21 3:48 ` 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=20080619181945.2b242e4d@extreme \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=wangchen@cn.fujitsu.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).