From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: netdev@vger.kernel.org, per.liden@ericsson.com,
jon.maloy@ericsson.com, allan.stephens@windriver.com
Subject: Re: [PATCH] TIPC: fix two minor sparse warnings
Date: Thu, 02 Aug 2007 19:28:18 -0700 (PDT) [thread overview]
Message-ID: <20070802.192818.53337859.davem@davemloft.net> (raw)
In-Reply-To: <20070802225756.GA14999@Chamillionaire.breakpoint.cc>
From: Florian Westphal <fw@strlen.de>
Date: Fri, 3 Aug 2007 00:57:56 +0200
> fix two warnings generated by sparse:
>
> link.c:2386 symbol 'msgcount' shadows an earlier one
> node.c:244 symbol 'addr_string' shadows an earlier one
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
Looks good, applied, thanks Florian.
prev parent reply other threads:[~2007-08-03 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 22:57 [PATCH] TIPC: fix two minor sparse warnings Florian Westphal
2007-08-03 2:28 ` David Miller [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=20070802.192818.53337859.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=allan.stephens@windriver.com \
--cc=fw@strlen.de \
--cc=jon.maloy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=per.liden@ericsson.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).