From: Sasha Levin <levinsasha928@gmail.com>
To: Krishna Kumar2 <krkumar2@in.ibm.com>
Cc: davem@davemloft.net, mst@redhat.com, netdev@vger.kernel.org,
rusty@rustcorp.com.au
Subject: Re: [PATCH] virtio_net: Give indication on device probe failure.
Date: Thu, 24 Nov 2011 11:24:13 +0200 [thread overview]
Message-ID: <1322126653.4248.10.camel@lappy> (raw)
In-Reply-To: <OF0C38CC5A.2D445246-ON65257952.002F945B-65257952.00301BA1@in.ibm.com>
On Thu, 2011-11-24 at 14:17 +0530, Krishna Kumar2 wrote:
> Sasha Levin <levinsasha928@gmail.com> wrote on 11/24/2011 02:05:22 PM:
>
> > > Provide an indication when the virtio_net device fails to
> > > initialize.
> > >
> > > Signed-off-by: Krishna Kumar <krkumar2@in.ibm.com>
> > > ---
> >
> > [snip]
> >
> > You already get a warning from the thingie that probes PCI:
> >
> > [ 1.166311] virtio_net: probe of virtio1 failed with error -12
>
> Ah, I created this patch based on your feedback:
>
> > I would suggest adding some output if we take the failure path, since
> > while the guest does boot peacefully, it doesn't have a network
> > interface and there's nothing in the boot log to indicate anything has
> > gone wrong.
>
> Is this probe error enough to find there was a problem,
> or do you think detailed error in all fail cases is
> required?
>
> Thanks,
>
> - KK
>
Nope, I must have missed that error. Sorry about that.
More warnings there can be useful, but it's true for the probe function
of all other virtio drivers as well :)
--
Sasha.
prev parent reply other threads:[~2011-11-24 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 8:24 [PATCH] virtio_net: Give indication on device probe failure Krishna Kumar
2011-11-24 8:35 ` Sasha Levin
2011-11-24 8:47 ` Krishna Kumar2
2011-11-24 9:24 ` Sasha Levin [this message]
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=1322126653.4248.10.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=davem@davemloft.net \
--cc=krkumar2@in.ibm.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.