Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030337AbXBTR2J (ORCPT ); Tue, 20 Feb 2007 12:28:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030330AbXBTR2J (ORCPT ); Tue, 20 Feb 2007 12:28:09 -0500 Received: from e34.co.us.ibm.com ([32.97.110.152]:50172 "EHLO e34.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030328AbXBTR2G (ORCPT ); Tue, 20 Feb 2007 12:28:06 -0500 Subject: Re: [PATCH 2.6.21-rc1] ibmebus: Support dynamic addition and removal of adapters From: John Rose To: Joachim Fenkes Cc: Hoang-Nam Nguyen , Me Notes , lkml , External List , Paul Mackerras , Paul Mackerras In-Reply-To: References: Content-Type: text/plain Message-Id: <1171992306.22669.5.camel@sinatra.austin.ibm.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 20 Feb 2007 11:25:06 -0600 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 877 Lines: 25 > If the probe operation succeeds, the respective device will show up > beneath > /sys/bus/ibmebus/devices. This approach is not particularly synchronous. Take the case of an add failure: how long would an application wait before deciding that the new device is not going to appear? It might be preferable to have the write to the probe function fail. For example, if we can't find the device node, return -EINVAL or something. > This is already taken care of by of_device_register(). If we are scrapping the use of of_device for ibmebus devices, can we still create a devspec file for OF correlation purposes? Thanks- John - 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/