From: Rusty Russell <rusty@rustcorp.com.au>
To: "Kay Sievers" <kay.sievers@vrfy.org>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
"Greg KH" <greg@kroah.com>
Subject: Re: virtio: struct device - replace bus_id with dev_name(), dev_set_name()
Date: Thu, 6 Nov 2008 22:18:36 +1100 [thread overview]
Message-ID: <200811062218.37128.rusty@rustcorp.com.au> (raw)
In-Reply-To: <ac3eb2510811052228o305b432cp2df9d311f103fc92@mail.gmail.com>
On Thursday 06 November 2008 17:28:56 Kay Sievers wrote:
> On Thu, Nov 6, 2008 at 04:45, Rusty Russell <rusty@rustcorp.com.au> wrote:
> > I'm curious how you're going to handle out-of-memory conditions?
>
> If the name can't be set, the following call to device_register() will
> fail, and should be handled by the caller. Just like today when we
> allocate the kobject name in device_register(). After the core has
> switched over, the name allocation will only happen a few lines
> earlier, it should not behave different otherwise. Is that what you
> mean?
Yep, thanks. Sounds fine.
Rusty.
prev parent reply other threads:[~2008-11-06 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 19:10 virtio: struct device - replace bus_id with dev_name(), dev_set_name() Kay Sievers
2008-11-06 3:45 ` Rusty Russell
2008-11-06 6:28 ` Kay Sievers
2008-11-06 11:18 ` Rusty Russell [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=200811062218.37128.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@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.