Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753824AbYKFG3P (ORCPT ); Thu, 6 Nov 2008 01:29:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751443AbYKFG27 (ORCPT ); Thu, 6 Nov 2008 01:28:59 -0500 Received: from ey-out-2122.google.com ([74.125.78.27]:49233 "EHLO ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750865AbYKFG27 (ORCPT ); Thu, 6 Nov 2008 01:28:59 -0500 Message-ID: Date: Thu, 6 Nov 2008 07:28:56 +0100 From: "Kay Sievers" To: "Rusty Russell" Subject: Re: virtio: struct device - replace bus_id with dev_name(), dev_set_name() Cc: linux-kernel , "Greg KH" In-Reply-To: <200811061445.12050.rusty@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1225393822.21973.39.camel@nga.site> <200811061445.12050.rusty@rustcorp.com.au> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1103 Lines: 27 On Thu, Nov 6, 2008 at 04:45, Rusty Russell 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/