[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac3eb2510811052228o305b432cp2df9d311f103fc92@mail.gmail.com>
Date: Thu, 6 Nov 2008 07:28:56 +0100
From: "Kay Sievers" <kay.sievers@...y.org>
To: "Rusty Russell" <rusty@...tcorp.com.au>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
"Greg KH" <greg@...ah.com>
Subject: Re: virtio: struct device - replace bus_id with dev_name(), dev_set_name()
On Thu, Nov 6, 2008 at 04:45, Rusty Russell <rusty@...tcorp.com.au> wrote:
> On Friday 31 October 2008 06:10:22 Kay Sievers wrote:
>> This patch is part of a larger patch series which will remove
>> the "char bus_id[20]" name string from struct device. The device
>> name is managed in the kobject anyway, and without any size
>> limitation, and just needlessly copied into "struct device".
>
> OK, I've applied this patch.
Thanks!
> 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?
Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists