Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754576AbYKFLSp (ORCPT ); Thu, 6 Nov 2008 06:18:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753467AbYKFLSg (ORCPT ); Thu, 6 Nov 2008 06:18:36 -0500 Received: from ozlabs.org ([203.10.76.45]:37570 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753529AbYKFLSg (ORCPT ); Thu, 6 Nov 2008 06:18:36 -0500 From: Rusty Russell To: "Kay Sievers" Subject: Re: virtio: struct device - replace bus_id with dev_name(), dev_set_name() Date: Thu, 6 Nov 2008 22:18:36 +1100 User-Agent: KMail/1.9.10 Cc: "linux-kernel" , "Greg KH" References: <1225393822.21973.39.camel@nga.site> <200811061445.12050.rusty@rustcorp.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811062218.37128.rusty@rustcorp.com.au> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 841 Lines: 19 On Thursday 06 November 2008 17:28:56 Kay Sievers wrote: > On Thu, Nov 6, 2008 at 04:45, Rusty Russell 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/