From: David Miller <davem@davemloft.net>
To: kaber@trash.net
Cc: nix.or.die@googlemail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: net/ipv4/inetpeer.c stack warnings
Date: Fri, 20 Jul 2007 19:39:26 -0700 (PDT) [thread overview]
Message-ID: <20070720.193926.92584343.davem@davemloft.net> (raw)
In-Reply-To: <469F5DBB.3080106@trash.net>
From: Patrick McHardy <kaber@trash.net>
Date: Thu, 19 Jul 2007 14:48:59 +0200
> Gabriel C wrote:
> > Hello ,
> >
> > I noticed on current git this warning in net/ipv4/inetpeer.c
>
> Yeah, I have no idea why the gcc people thought that this was
> something worth warning about. Especially since explicitly
> checking for != NULL silences the warning again.
Sigh, applied :-)
next prev parent reply other threads:[~2007-07-21 2:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 12:29 net/ipv4/inetpeer.c stack warnings Gabriel C
2007-07-19 12:48 ` Patrick McHardy
2007-07-19 13:10 ` Gabriel C
2007-07-21 2:39 ` David Miller [this message]
2007-07-19 21:16 ` 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=20070720.193926.92584343.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nix.or.die@googlemail.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).