All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Patch: allow a fixed port for TFTP (take 3)
Date: Tue, 11 Jan 2005 17:47:11 -0600	[thread overview]
Message-ID: <41E4657F.6010406@orkun.us> (raw)
In-Reply-To: <20050111224928.7BE88C108D@atlas.denx.de>

Dear Wolfgang,

Wolfgang Denk wrote:
> In message <41E3ECBA.5030802@smiths-aerospace.com> you wrote:
> 
>>Hi Wolfgang, try three on the patch attached.  The change here is to 
>>rename the env variable per Tolunay Orkun's recommendation.
> 
> 
> I reject this because such a long variable name seems unacceptable to
> me. Don't make life unnecessarily hard to your  users.  Use  a  short
> name. How about "tftpport"?

Wolfgang, "tftpport" is what he has done previously.

It is more appropriate and customary for "tftpport" to refer to the 
server port (i.e. reference to a port without a qualification of 
client/server, source/destination etc). This patch on the other hand is 
leaving the server port as is (well known port) and modifying the 
normally dynamic source (client) port to a fixed value via environment. 
I think, using "tftpport" would be a poor choice.

I will pledge for clarity over 6 more bytes in environment which most 
boards will not define anyway. If that is not reasonable, please allow 
for "tftpsrcport" or "tftpcport".

I actually want to provide a complimentary patch over this one to make 
the tftp server port configurable which the environment variable can be 
appropriately named as one of "tftpserverport", "tftpdestport" or 
"tftpsport". I also want to use the same CONFIG_TFTP_PORT variable to 
enable both environment variables unless you object in which case naming 
the config variables as CONFIG_TFTP_CLIENT_PORT and 
CONFIG_TFTP_SERVER_PORT is probably better.

Best regards,
Tolunay

  reply	other threads:[~2005-01-11 23:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 15:11 [U-Boot-Users] Patch: allow a fixed port for TFTP (take 3) Jerry Van Baren
2005-01-11 22:49 ` Wolfgang Denk
2005-01-11 23:47   ` Tolunay Orkun [this message]
2005-01-12  0:10     ` Wolfgang Denk
2005-01-12  8:09       ` Tolunay Orkun
2005-01-12 13:40         ` Jerry Van Baren
2005-01-12 16:11           ` Tolunay Orkun
2005-09-24 20:47           ` Wolfgang Denk
2005-09-24 21:26             ` Wolfgang Denk
2005-01-12 14:01         ` Wolfgang Denk
2005-01-12 12:33   ` Jerry Van Baren

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=41E4657F.6010406@orkun.us \
    --to=listmember@orkun.us \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.