In message 41E4657F.6010406@orkun.us you wrote:
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.
:-(
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".
So be it "tftpsrcport" then. Or "tftpsrcp" :-)
["tftpcport" ??? TFT-PC-Port? Or 'c' like what???]
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
tftpdstport or tftpdstp, please.
"tftpsport". I also want to use the same CONFIG_TFTP_PORT variable to
[Seems to be some funny kind of exercise, this: TFTP sport. And is misleading - TFTP _S_ource Port ?]
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.
OK.
Best regards,
Wolfgang Denk