public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: Greg KH <greg@kroah.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
	jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH, v2] PCI: create function symlinks in /sys/bus/pci/slots/N/
Date: Tue, 26 Aug 2008 21:50:03 -0600	[thread overview]
Message-ID: <20080827035003.GA25140@ldl.fc.hp.com> (raw)
In-Reply-To: <20080825040713.GE3128@kroah.com>

* Greg KH <greg@kroah.com>:
> On Sat, Aug 23, 2008 at 02:04:46PM -0600, Alex Chiang wrote:
> 
> > Did you get a chance to take a look at the documentation I wrote
> > for these new symlinks? [I also went and documented the existing
> > slots/ directory as well...]
> > 
> > Was it what you had in mind?
> 
> Yes, it looked very good.

Thanks.

> And thanks for the other documentation as well, if you want,
> you could split that out as a different patch and odds are
> Jesse could get that into the tree before 2.6.27 comes out :)

Hrm, given the harder line Linus has taken against "regression
only" patches lately, it can probably wait another release cycle.

After all, it's been un-documented since pre-git history anyway.
;)

Thanks.

/ac


  reply	other threads:[~2008-08-27  3:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22 16:20 [PATCH, v2] PCI: create function symlinks in /sys/bus/pci/slots/N/ Alex Chiang
2008-08-22 18:23 ` Matthew Wilcox
2008-08-22 19:53   ` Alex Chiang
2008-08-23 15:44     ` Greg KH
2008-08-23 20:04       ` Alex Chiang
2008-08-25  4:07         ` Greg KH
2008-08-27  3:50           ` Alex Chiang [this message]
2008-08-27  4:01             ` Greg KH
2008-08-27 14:21               ` Matthew Wilcox
2008-08-27 15:04                 ` Greg KH
2008-08-27 22:44                   ` Jesse Barnes

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=20080827035003.GA25140@ldl.fc.hp.com \
    --to=achiang@hp.com \
    --cc=greg@kroah.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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