From: Greg KH <greg@kroah.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Alex Chiang <achiang@hp.com>,
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: Wed, 27 Aug 2008 08:04:38 -0700 [thread overview]
Message-ID: <20080827150438.GA30929@kroah.com> (raw)
In-Reply-To: <20080827142139.GB19788@parisc-linux.org>
On Wed, Aug 27, 2008 at 08:21:39AM -0600, Matthew Wilcox wrote:
> On Tue, Aug 26, 2008 at 09:01:35PM -0700, Greg KH wrote:
> > On Tue, Aug 26, 2008 at 09:50:03PM -0600, Alex Chiang wrote:
> > > * Greg KH <greg@kroah.com>:
> > > > 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.
> >
> > Documentation updates and new stand-alone drivers are ok at all times :)
>
> You're clearly not hanging on every word of our Dear Leader:
>
> http://marc.info/?l=linux-kernel&m=121924636529367&w=2
I read that, and parsed:
I generally won't complain about them, but I also don't see the
point.
as being up to the maintainer's judgement.
So in this case, it's up to Jesse :)
thanks,
greg k-h
next prev parent reply other threads:[~2008-08-27 15:07 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
2008-08-27 4:01 ` Greg KH
2008-08-27 14:21 ` Matthew Wilcox
2008-08-27 15:04 ` Greg KH [this message]
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=20080827150438.GA30929@kroah.com \
--to=greg@kroah.com \
--cc=achiang@hp.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