From: Duncan Hare <dh@synoia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v8 1/3] Adding TCP and wget into u-boot
Date: Mon, 19 Mar 2018 14:11:34 -0700 [thread overview]
Message-ID: <20180319141134.74318e35@raspberrypi> (raw)
In-Reply-To: <DB6PR04MB31288114038A6C8D24EF507C93D40@DB6PR04MB3128.eurprd04.prod.outlook.com>
On Mon, 19 Mar 2018 09:53:24 +0000
Calvin Johnson <calvin.johnson@nxp.com> wrote:
>
> > > > void net_set_udp_header(uchar *pkt, struct in_addr dest, int
> > > > dport,
> > > > - int sport, int len);
> > > > -
> > > > + int sport, int len);
> > >
> > Why do you need this change in the set_udp_header?
> >
> > This is a shim to bridge between the original udp to ip procedure
> > call and the extra parameters in the enhanced ip procedure call to
> > the ip layer for TCP.
> >
> > The original udp call is unchanged, because I did not want a
> > change to a procedure call to ripple through many applications.
>
> For now, I'm okay with the change you made to net_set_ip_header.
>
> - int sport, int len);
> -
> + int sport, int len);
> I'm concerned about above 3 line change. Here, you are decreasing
> indent and removing an empty line. This change may not be required.
yes, I don't remember this, but its probably driven by patman messages.
These are both issues which can generated patman error messages.
Duncan
prev parent reply other threads:[~2018-03-19 21:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 4:43 [U-Boot] [PATCH v8 1/3] Adding TCP and wget into u-boot DH at synoia.com
2018-03-08 4:43 ` [U-Boot] [PATCH v8 2/3] Adding TCP DH at synoia.com
2018-03-08 18:53 ` Joe Hershberger
2018-03-08 4:43 ` [U-Boot] [PATCH v8 3/3] Adding wget DH at synoia.com
2018-03-08 18:52 ` [U-Boot] [PATCH v8 1/3] Adding TCP and wget into u-boot Joe Hershberger
2018-03-17 13:55 ` Calvin Johnson
2018-03-17 16:36 ` Calvin Johnson
2018-03-18 23:10 ` Duncan Hare
2018-03-19 9:53 ` Calvin Johnson
2018-03-19 21:11 ` Duncan Hare [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=20180319141134.74318e35@raspberrypi \
--to=dh@synoia.com \
--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