From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265045AbUBDXoQ (ORCPT ); Wed, 4 Feb 2004 18:44:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264383AbUBDXoJ (ORCPT ); Wed, 4 Feb 2004 18:44:09 -0500 Received: from mail.kroah.org ([65.200.24.183]:40378 "EHLO perch.kroah.org") by vger.kernel.org with ESMTP id S264954AbUBDXlO (ORCPT ); Wed, 4 Feb 2004 18:41:14 -0500 Date: Wed, 4 Feb 2004 15:38:40 -0800 From: Greg KH To: Linus Torvalds Cc: Benjamin Herrenschmidt , Linux Kernel list , Andrew Morton Subject: Re: [PATCH] PCI / OF linkage in sysfs Message-ID: <20040204233840.GA5375@kroah.com> References: <1075878713.992.3.camel@gaston> <20040204231324.GA5078@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 04, 2004 at 03:28:21PM -0800, Linus Torvalds wrote: > > On Wed, 4 Feb 2004, Greg KH wrote: > > > > Or, if you really want to be able to get the OF info from the pci device > > in sysfs, why not create a symlink in the pci device directory pointing > > to your OF path in sysfs? That would seem like the best option. > > Where does this stop? Do we start doing the same for all different kinds > of buses, and all kinds of firmware? Ok, good point. You're right in that way we would eventually end up with a huge mess... Sorry Ben. greg k-h