netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel C <nix.or.die@googlemail.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: net/ipv4/inetpeer.c stack warnings
Date: Thu, 19 Jul 2007 15:10:40 +0200	[thread overview]
Message-ID: <469F62D0.4030003@googlemail.com> (raw)
In-Reply-To: <469F5DBB.3080106@trash.net>

Patrick McHardy wrote:
> 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.
>
>
>   

Thx , the patch fixes that for me.

Gabriel

  reply	other threads:[~2007-07-19 13:12 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 [this message]
2007-07-21  2:39   ` David Miller
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=469F62D0.4030003@googlemail.com \
    --to=nix.or.die@googlemail.com \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --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).