From: Tom Rini Date: Tue, 19 Jan 2021 15:01:00 -0500 Subject: [PATCH] net: tftp: Fix incorrect tftp_next_ack on no OACK In-Reply-To: <78b5cf7788fb9ed24bd407105f750a8ff73af324.camel@nedap.com> References: <78b5cf7788fb9ed24bd407105f750a8ff73af324.camel@nedap.com> Message-ID: <20210119200100.GN9782@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, Nov 27, 2020 at 09:45:56PM +0000, Harm Berntsen wrote: > When the tftp server did not send any OACK, the tftp_next_ack variable > was not set to the correct value . As the server was transmitting > blocks we generated a lot of 'Received unexpected block: $n, expected > $n+1' error messages. Depending on the timeout setting the transfer > could still complete though. > > Signed-off-by: Harm Berntsen > CC: Ramon Fried > Reviewed-By: Ramon Fried Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: