All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Erwan Velu <erwanaliasr1@gmail.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [PATCH V2] ipconfig: Inform user if carrier is not ready
Date: Fri, 14 Sep 2012 12:19:46 -0700	[thread overview]
Message-ID: <50538352.6080406@hp.com> (raw)
In-Reply-To: <505380A0.7020407@gmail.com>

On 09/14/2012 12:08 PM, Erwan Velu wrote:
> From: Erwan Velu <erwanaliasr1@gmail.com>
>
> While using the ip= option at the cmdline, the kernel can hold the boot
> process for 2 minutes (CONF_CARRIER_TIMEOUT) if the carrier is not
> present.
>
> While waiting the carrier, user is not informed about this situation and
> so could think the kernel is frozen.
>
> If we don't get the carrier after some seconds, let's display a message to
> inform the user about the remaining time before reaching the timeout.

That should be much better than upwards of 120 messages.

rick jones

  parent reply	other threads:[~2012-09-14 19:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 20:21 Remarks and comments about ipconfig behavior Erwan Velu
2012-09-13 20:31 ` David Miller
2012-09-13 20:37   ` Erwan Velu
2012-09-13 20:45     ` David Miller
2012-09-13 21:59       ` [PATCH] ipconfig: Inform user if carrier is not ready Erwan Velu
2012-09-14  5:36         ` Francois Romieu
     [not found]         ` <50525C5D.8040302@hp.com>
2012-09-14 19:08           ` [PATCH V2] " Erwan Velu
2012-09-14 19:17             ` David Miller
2012-09-14 19:30               ` [PATCH V3] " Erwan Velu
2012-09-14 19:42                 ` David Miller
2012-09-14 20:13                   ` Erwan Velu
2012-09-14 20:23                     ` David Miller
2012-09-14 20:59                       ` Erwan Velu
2012-09-14 19:31               ` [PATCH V2] " Erwan Velu
2012-09-14 19:19             ` Rick Jones [this message]
2012-09-15 16:18   ` Remarks and comments about ipconfig behavior Erwan Velu

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=50538352.6080406@hp.com \
    --to=rick.jones2@hp.com \
    --cc=davem@davemloft.net \
    --cc=erwanaliasr1@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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.