public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@redhat.com>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Anton Blanchard <anton@samba.org>,
	David Mosberger <davidm@hpl.hp.com>
Subject: Re: [PATCH] reimplement pci proc name
Date: Fri, 20 Jun 2003 14:24:13 -0700	[thread overview]
Message-ID: <20030620212413.GA13694@kroah.com> (raw)
In-Reply-To: <20030620134811.GR24357@parcelfarce.linux.theplanet.co.uk>

On Fri, Jun 20, 2003 at 02:48:11PM +0100, Matthew Wilcox wrote:
> 
> Hi Greg.  Ivan's not happy with the solution I came up with for naming
> /proc/bus/pci and Anton would prefer something slightly different too,
> so I abstracted the name out so each architecture can do its own thing.
> 
> This is against 2.5.72 so won't apply cleanly to your tree (it
> applies to bitkeeper as of a few minutes ago with only minor offsets).
> I've implemented the original name for non-PCI-domain machines; done what
> ia64 and alpha need, respectively (assuming I didn't misunderstand Ivan),
> and plopped in the Old Way of doing things for Sparc64, PPC and PPC64.
> Maintainers may alter this to whatever degree of complexity they wish.

Thanks, I've reverted your previous patch, and fixed the one typo in
this patch and applied it all to my bk tree.  Hopefully Linus will pull
from it sometime soon :)

thanks,

greg k-h

  parent reply	other threads:[~2003-06-20 21:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-20 13:48 [PATCH] reimplement pci proc name Matthew Wilcox
2003-06-20 14:02 ` Martin Zwickel
2003-06-20 14:11   ` Matthew Wilcox
2003-06-20 14:06 ` Ivan Kokshaysky
2003-06-20 21:24 ` Greg KH [this message]
2003-06-21 11:53   ` Ivan Kokshaysky
2003-06-23  2:44     ` 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=20030620212413.GA13694@kroah.com \
    --to=greg@kroah.com \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=davem@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=ink@jurassic.park.msu.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox