mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH very-draft] add ifconfig command
Date: Wed, 3 Aug 2011 16:01:08 +0400	[thread overview]
Message-ID: <CAA4bVAGnCxcaF9+Toh13VEzKxET+nW3dvbk5La9zRsnMnot9CA@mail.gmail.com> (raw)
In-Reply-To: <20110803102244.GQ31404@pengutronix.de>

On 3 August 2011 14:22, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Wed, Aug 03, 2011 at 12:28:42PM +0400, Antony Pavlov wrote:
>> Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
>> ---
>>  commands/Kconfig    |    6 +++
>>  commands/Makefile   |    1 +
>>  commands/ifconfig.c |   97 +++++++++++++++++++++++++++++++++++++++++++++++++++
>>  3 files changed, 104 insertions(+), 0 deletions(-)
>>  create mode 100644 commands/ifconfig.c
>
> Right now I don't see the reason to add a ifconfig command. Why not use
> devinfo eth0?

I don't use dhcp.
I use enhanced version of ifconfig to setup eth0 parameters
(ipaddr, netmask etc).

Have we a command to make dev_set_param() on any device?

With command of such type we will have no need of ifconfig.

-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2011-08-03 12:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03  8:28 [PATCH very-draft] lib: add hexdump function from linux-3.0 Antony Pavlov
2011-08-03  8:28 ` [PATCH very-draft] add ifconfig command Antony Pavlov
2011-08-03 10:22   ` Sascha Hauer
2011-08-03 12:01     ` Antony Pavlov [this message]
2011-08-03 12:06       ` Sascha Hauer
2011-08-03 13:48         ` Antony Pavlov
2011-08-03 10:21 ` [PATCH very-draft] lib: add hexdump function from linux-3.0 Sascha Hauer

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=CAA4bVAGnCxcaF9+Toh13VEzKxET+nW3dvbk5La9zRsnMnot9CA@mail.gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.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