From: Sam Ravnborg <sam@ravnborg.org>
To: "Stephens, Allan" <allan.stephens@windriver.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 03/08] [TIPC]: Eliminate "sparse" warning in socket code
Date: Fri, 22 Feb 2008 21:04:25 +0100 [thread overview]
Message-ID: <20080222200425.GC7154@uranus.ravnborg.org> (raw)
In-Reply-To: <AF1602CB2550CE4381C0C75118A7856B0246C891@ala-mail02.corp.ad.wrs.com>
On Fri, Feb 22, 2008 at 11:59:12AM -0800, Stephens, Allan wrote:
> This patch eliminates warnings about a pair of undeclared symbols.
Hi Allan.
Last I looked there where ~90 sparse warnings for tipc.
I assume you are aware and that they are getting fixed.
Sam - who would like to see an almost sparse clean kernel
next prev parent reply other threads:[~2008-02-22 20:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 19:59 [PATCH 03/08] [TIPC]: Eliminate "sparse" warning in socket code Stephens, Allan
2008-02-22 20:04 ` Sam Ravnborg [this message]
2008-02-22 20:10 ` Stephens, Allan
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=20080222200425.GC7154@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=allan.stephens@windriver.com \
--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).