From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Dongdong Deng <dongdong.deng@windriver.com>,
<davem@davemloft.net>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Subject: Re: [Bridge] [PATCH] bridge: return value for br_stp_recalculate_bridge_id()
Date: Thu, 31 Mar 2011 15:31:00 -0700 [thread overview]
Message-ID: <20110331153100.44b02f86.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110331103822.39b1a89e@nehalam>
On Thu, 31 Mar 2011 10:38:22 -0700
Stephen Hemminger <shemminger@vyatta.com> wrote:
> Reported 3 times and already fixed.
Four times!
Heaven knows why gcc treats that as a warning and not an error. It's a
guaranteed runtime bug.
prev parent reply other threads:[~2011-03-31 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 6:23 [PATCH] bridge: return value for br_stp_recalculate_bridge_id() Dongdong Deng
2011-03-30 6:27 ` Stephen Hemminger
2011-03-31 17:38 ` [Bridge] " Stephen Hemminger
2011-03-31 22:31 ` Andrew Morton [this message]
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=20110331153100.44b02f86.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dongdong.deng@windriver.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).