From: Stephen Hemminger <shemminger@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, bridge@linux-foundation.org
Subject: [PATCH 0/4] bridge patches
Date: Wed, 21 Feb 2007 14:41:07 -0800 [thread overview]
Message-ID: <20070221224107.741532037@linux-foundation.org> (raw)
Several patches to bridge. #1 is a nit, #2 is a bug fix,
#3 and #4 are manageability enhancements (they can wait for
2.6.22 if needed).
--
Stephen Hemminger <shemminger@linux-foundation.org>
next reply other threads:[~2007-02-21 22:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 22:41 Stephen Hemminger [this message]
2007-02-21 22:41 ` [PATCH 1/4] bridge: get rid of miscdevice include Stephen Hemminger
2007-02-21 23:40 ` Marc.Obbad
2007-02-22 9:09 ` David Miller
2007-02-21 22:41 ` [PATCH 2/4] bridge: eliminate workqueue for carrier check Stephen Hemminger
2007-02-22 9:10 ` David Miller
2007-02-21 22:41 ` [PATCH 3/4] bridge: make path cost setting persistent Stephen Hemminger
2007-02-27 17:52 ` [PATCH 3+/4] bridge: fix locking of set path cost Stephen Hemminger
2007-02-27 17:56 ` David Miller
2007-02-21 22:41 ` [PATCH 4/4] bridge: add flush attribute Stephen Hemminger
2007-02-22 9:11 ` [PATCH 0/4] bridge patches 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=20070221224107.741532037@linux-foundation.org \
--to=shemminger@linux-foundation.org \
--cc=bridge@linux-foundation.org \
--cc=davem@davemloft.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 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).