From: Cyrill Gorcunov <gorcunov@openvz.org>
To: shemminger@linux-foundation.org, kaber@trash.net,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: [patch 0/2] a few bridge code cleanups
Date: Sat, 04 Jul 2009 10:11:56 +0400 [thread overview]
Message-ID: <20090704061156.658235360@openvz.org> (raw)
Hi,
here is a few bridge cleanups - code alignment
and conditional compilation for structure members.
Please review. Hope I didn't miss anything.
Anyway if it breaks someone patch queue --
just drop this series then.
Cyrill
next reply other threads:[~2009-07-04 6:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-04 6:11 Cyrill Gorcunov [this message]
2009-07-04 6:11 ` [patch 1/2] net, bridge: align br_nf_ops assignment Cyrill Gorcunov
2009-07-09 19:55 ` Stephen Hemminger
2009-07-11 14:30 ` Cyrill Gorcunov
2009-07-04 6:11 ` [patch 2/2] net, netns_xt: shrink netns_xt members Cyrill Gorcunov
2009-07-09 19:55 ` Stephen Hemminger
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=20090704061156.658235360@openvz.org \
--to=gorcunov@openvz.org \
--cc=bridge@lists.linux-foundation.org \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).