From: Gray Remlin <gryrmln@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: Add support for displaying second ethaddr in 'bdinfo' command
Date: Tue, 29 Mar 2011 23:36:22 +0100 [thread overview]
Message-ID: <4D925EE6.50305@gmail.com> (raw)
In-Reply-To: <20110329214930.12634EDFFCF@gemini.denx.de>
On 03/29/2011 10:49 PM, Wolfgang Denk wrote:
> Dear Gray Remlin,
>
> In message<1301433395-25203-1-git-send-email-gryrmln@gmail.com> you wrote:
>> Signed-off-by: Gray Remlin<gryrmln@gmail.com>
>> ---
>> common/cmd_bdinfo.c | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
> Why limit this to eth1addr? What's the chances that ARM systems may
> have more than 2 network interfaces?
>
> Best regards,
>
> Wolfgang Denk
>
Good question, I have already asked myself this, so I have stuck with
what I do know.
1. It has had the one ethaddr limit for a (relatively) long time, which
it seems no-one else 'required'\'submitted a patch' to change it.
2. I only know (with my very limited knowledge) of ARM boards with a
maximum of two interfaces as standard.
3. Why limit it to six (as in other parts of the source) ?
My answer:
It is not my place to dictate policy, that is the role of the Project
Manager.
And no, that is not a 'cop-out', it is the only way to avoid anarchy.
next prev parent reply other threads:[~2011-03-29 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 21:16 [U-Boot] [PATCH] ARM: Add support for displaying second ethaddr in 'bdinfo' command Gray Remlin
2011-03-29 21:49 ` Wolfgang Denk
2011-03-29 22:36 ` Gray Remlin [this message]
2011-03-30 11:34 ` Albert ARIBAUD
2011-03-30 13:35 ` Gray Remlin
2011-03-30 12:47 ` Detlev Zundel
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=4D925EE6.50305@gmail.com \
--to=gryrmln@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