From: Reinhard Arlt <reinhard.arlt@t-online.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Strange code in NetReceive(..) in net.c
Date: Mon, 09 May 2005 10:12:11 +0200 [thread overview]
Message-ID: <427F1B5B.7010603@t-online.de> (raw)
In-Reply-To: <20050502204440.B868FC1510@atlas.denx.de>
Hello,
here is the patch for the two missing statements.
Reinhard
Wolfgang Denk wrote:
> In message <427683E5.5050608@t-online.de> you wrote:
>
>>if you look at the code for ICMP handling in NetReceive, you will see that:
>
>
> Which version of the code are you talking about?
1.1.2
>
>
>>-- For an ICMP_REDIR_HOST packet, the nc_input_packet code and then the
>>(*packetHandler) is called.
>>
>>-- For an ICMP_ECHO_REPLY, the (*packetHandler) is called twice.
>>
>>Is this is not intended, i can prepare a patch.
>
>
> We should probably have "return"s in both "case"s. Lokking forward to
> see your patch.
>
>
>>A "return" before the "break" in the ICMP_PROTO path and an "return"
>>before the "break" in the ICMP_ECHO_REPLY path will do it.
>
>
> Agreed.
>
> Best regards,
>
> Wolfgang Denk
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Changelog
Url: http://lists.denx.de/pipermail/u-boot/attachments/20050509/ac73d6e7/attachment.txt
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: net_missing_return_patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20050509/ac73d6e7/attachment-0001.txt
prev parent reply other threads:[~2005-05-09 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 19:47 [U-Boot-Users] Strange code in NetReceive(..) in net.c Reinhard Arlt
2005-05-02 20:44 ` Wolfgang Denk
2005-05-09 8:12 ` Reinhard Arlt [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=427F1B5B.7010603@t-online.de \
--to=reinhard.arlt@t-online.de \
--cc=u-boot@lists.denx.de \
/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