All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org, willy@debian.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [PATCH] add legacy resources to sysfs
Date: Tue, 21 Dec 2004 16:05:09 -0800	[thread overview]
Message-ID: <20041222000509.GA12595@kroah.com> (raw)
In-Reply-To: <200412211542.47997.jbarnes@engr.sgi.com>

On Tue, Dec 21, 2004 at 03:42:47PM -0800, Jesse Barnes wrote:
> On Tuesday, December 21, 2004 2:05 pm, Jesse Barnes wrote:
> > On Tuesday, December 21, 2004 1:46 pm, Greg KH wrote:
> > > You are passing the wrong things around :)
> > >
> > > A struct pci_bus is a struct class_device, not a struct device.  I think
> > > you need to rethink your goal of putting the files into the pci device
> > > directory, or just put the files into the proper /sys/class/pci_bus/*
> > > directory as your code assumes is happening.
> >
> > Something like this then?  I added bin file support to class.c and use that
> > instead from probe.c.  I also fixed the container_of stuff in pci-sysfs.c.
> 
> Here it is w/o the ia64 stuff.  That way people can buy off on the API and not 
> worry about the platform stuff.  I can send that to Tony separately if 
> there's agreement on this part.  I'd like to create a symlink 
> from /sys/class/pci_bus/<bus>/legacy_* to /sys/devices/pci<foo>/legacy_* too, 
> how do I do that?

You can make a symlink to a kobject, not a attribute.  We already have a
symlink in that directory to the device, so do you really need another
one?

>  drivers/base/class.c    |   16 ++++++++++

Hm, how about splitting this further, one for the driver core stuff (you
forgot the device.h change here too...) and the other for the PCI stuff?

thanks,

greg k-h

  reply	other threads:[~2004-12-22  0:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21 20:47 [PATCH] add legacy resources to sysfs Jesse Barnes
2004-12-21 20:47 ` Jesse Barnes
2004-12-21 21:28 ` Matthew Wilcox
2004-12-21 21:28   ` Matthew Wilcox
2004-12-21 21:44   ` Greg KH
2004-12-21 21:44     ` Greg KH
2004-12-21 21:49   ` Jesse Barnes
2004-12-21 21:49     ` Jesse Barnes
2004-12-21 21:46 ` Greg KH
2004-12-21 21:46   ` Greg KH
2004-12-21 22:05   ` Jesse Barnes
2004-12-21 22:05     ` Jesse Barnes
2004-12-21 23:42     ` Jesse Barnes
2004-12-22  0:05       ` Greg KH [this message]
2004-12-22  0:14         ` Jesse Barnes
2004-12-22  0:20           ` Greg KH
2004-12-22  8:38   ` Benjamin Herrenschmidt
2004-12-22  8:38     ` Benjamin Herrenschmidt
2004-12-22 16:09     ` Greg KH
2004-12-22 16:09       ` Greg KH
2004-12-22 16:34       ` Benjamin Herrenschmidt
2004-12-22 16:34         ` Benjamin Herrenschmidt
2004-12-22 16:58         ` Jesse Barnes
2004-12-22 16:58           ` Jesse Barnes
2004-12-22 18:31           ` Jesse Barnes
2004-12-22 18:31             ` Jesse Barnes
2004-12-22 21:07             ` Greg KH
2004-12-22 21:07               ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041222000509.GA12595@kroah.com \
    --to=greg@kroah.com \
    --cc=benh@kernel.crashing.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.