From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] tftp warning/error?
Date: Thu, 14 Feb 2008 09:41:18 -0500 [thread overview]
Message-ID: <47B4530E.5050108@gmail.com> (raw)
In-Reply-To: <F83318C2-EB31-4073-84D3-195F220967D8@freescale.com>
Kumar Gala wrote:
> 'TFTP: add host ip addr support' commit added this bit of code which
> seems bogus:
>
> } else {
> char *p = strchr (p, ':');
>
> Is this really correct?
>
> - k
>
>
That's F-d up. The patches I have are like this:
- tftp_filename = BootFile;
+ char *p=BootFile;
+ p = strchr (p, ':');
but never got pulled into the net branch. I guess Wolfgang must have
pulled directly. C'mon patch management system!!!
cheers,
Ben
prev parent reply other threads:[~2008-02-14 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 20:57 [U-Boot-Users] tftp warning/error? Kumar Gala
2008-02-14 6:54 ` Jean-Christophe PLAGNIOL-VILLARD
2008-02-14 7:02 ` [U-Boot-Users] [PATCH] TFTP: fix search of ':' in BootFile Jean-Christophe PLAGNIOL-VILLARD
2008-02-14 7:34 ` Kumar Gala
2008-02-14 22:10 ` Wolfgang Denk
2008-02-14 22:19 ` Wolfgang Denk
2008-02-14 14:41 ` Ben Warren [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=47B4530E.5050108@gmail.com \
--to=biggerbadderben@gmail.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