Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966055AbXHaRrR (ORCPT ); Fri, 31 Aug 2007 13:47:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965634AbXHaRrF (ORCPT ); Fri, 31 Aug 2007 13:47:05 -0400 Received: from mtagate1.de.ibm.com ([195.212.29.150]:59948 "EHLO mtagate1.de.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965619AbXHaRrC (ORCPT ); Fri, 31 Aug 2007 13:47:02 -0400 In-Reply-To: <200708311908.05255.arnd@arndb.de> To: Arnd Bergmann Cc: Christoph Raisch , Jan-Bernd Themann , LKML , linuxppc-dev@ozlabs.org, Paul Mackerras , Paul Mackerras , Stefan Roscher , Thomas Q Klein MIME-Version: 1.0 Subject: Re: [PATCH 2.6.23] ibmebus: Prevent bus_id collisions X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006 From: Joachim Fenkes Message-ID: Date: Fri, 31 Aug 2007 19:46:58 +0200 X-MIMETrack: Serialize by Router on D12ML064/12/M/IBM(Release 7.0.2HF71 | November 3, 2006) at 31/08/2007 19:47:00, Serialize complete at 31/08/2007 19:47:00 Content-Type: text/plain; charset="US-ASCII" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 982 Lines: 24 > > The plaintiff makes a valid point. How about a staging approach: We put > > the patch as it is now into 2.6.23 so the problem is fixed, and I'll post > > a "nice" version with autoloading support and a generic of_make_bus_id > > function for 2.6.24. Agree? > > Ok, sounds fair. Can you make sure that the resulting bus_id is the same > for the final version then? No, it would change once more -- the current, minimal-invasive, variant of the fix uses the full_name -> "ehca@12345678", while of_make_bus_id uses another format: "12345678.ehca". I don't think this makes much of a difference, though, and users shouldn't rely on the bus_id having a certain format anyway, so IMHO we can live with this. Regards, Joachim - 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/