public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert.cahalan@ccur.com>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI changes and fixes for 2.5.72
Date: 20 Jun 2003 11:44:02 -0400	[thread overview]
Message-ID: <1056123842.986.60.camel@albertc> (raw)

Greg writes:

> [PATCH] PCI: Unconfuse /proc
>
> If we are to cope with multiple domains with clashing PCI bus
> numbers, we must refrain from creating two directories of the
> same name in /proc/bus/pci.  This is one solution to the
> problem; busses with a non-zero domain number get it prepended.
>
> Alternative solutions include cowardly refusing to create
> non-domain-zero bus directories, refusing to create directories
> with clashing names, and sticking our heads in the sand and
> pretending the problem doesn't exist.

Please don't do this. It's gross. As long as we have
the bus number mangling, stuff can stay as it is.
When the bus number mangling goes, the old-style
entries can go as well. I'm working on a patch that
makes the old-style entries be symlinks like this:

../../pci%d/bus%d/dev%d/fn%d/config-space

That solves the problem for good, in the right way.
It allows for migration to something sane.



             reply	other threads:[~2003-06-20 15:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-20 15:44 Albert Cahalan [this message]
2003-06-20 18:35 ` [PATCH] PCI changes and fixes for 2.5.72 Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-06-19 23:37 [BK PATCH] " Greg KH
2003-06-19 23:39 ` [PATCH] " Greg KH
2003-06-19 23:39   ` Greg KH
2003-06-19 23:39     ` Greg KH
2003-06-19 23:39       ` Greg KH
2003-06-19 23:39         ` Greg KH
2003-06-19 23:39           ` Greg KH
2003-06-19 23:39             ` Greg KH
2003-06-19 23:39               ` 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=1056123842.986.60.camel@albertc \
    --to=albert.cahalan@ccur.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox