From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Jon Mason <mason@myri.com>, Greg Kroah-Hartman <gregkh@suse.de>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Benjamin LaHaise <bcrl@kvack.org>
Subject: Re: [PATCH 2/3] pci: Clamp pcie_set_readrq() when using "performance" settings
Date: Wed, 5 Oct 2011 09:26:00 -0700 [thread overview]
Message-ID: <20111005092600.36d505b2@jbarnes-desktop> (raw)
In-Reply-To: <CA+55aFwoeC+X=XWWJ7HFUfz6tZmJW6PMmkGcRM5otLbyGt587Q@mail.gmail.com>
On Wed, 5 Oct 2011 07:49:24 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, Oct 5, 2011 at 12:01 AM, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> >
> >> We just don't the hell know, do we?
> >
> > Well, we do with some confidence :-) Or rather what we do know is what
> > you have today in your tree is broken.
>
> You're missing the point.
>
> Repeat after me: late -rc series is not when we test these kinds of things.
Yeah I think Ben just wants the convenience of having the non-default
code paths fixed when 3.1 comes out; but I agree we shouldn't be poking
around at all at this point.
Hopefully I'll get my kernel.org tree back up and running this week so
I can queue up the various fixes for the merge window. I'll do another
scan and ask people to send directly to you for the 2 or 3 things we
still have open for 3.1.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-10-05 16:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 14:50 [PATCH 2/3] pci: Clamp pcie_set_readrq() when using "performance" settings Jon Mason
2011-10-03 20:56 ` Linus Torvalds
2011-10-04 15:40 ` Benjamin Herrenschmidt
2011-10-04 15:48 ` Linus Torvalds
2011-10-04 15:56 ` Bjorn Helgaas
2011-10-04 16:08 ` Benjamin Herrenschmidt
2011-10-04 16:51 ` Linus Torvalds
2011-10-04 17:30 ` Benjamin Herrenschmidt
2011-10-04 17:36 ` Linus Torvalds
2011-10-05 7:01 ` Benjamin Herrenschmidt
2011-10-05 14:49 ` Linus Torvalds
2011-10-05 16:26 ` Jesse Barnes [this message]
2011-10-04 17:41 ` Benjamin LaHaise
2011-10-03 21:55 ` Jon Mason
2011-10-04 14:42 ` Benjamin LaHaise
2011-10-04 15:37 ` Benjamin LaHaise
2011-10-04 15:52 ` Benjamin Herrenschmidt
2011-10-04 15:59 ` Benjamin LaHaise
2011-10-04 16:19 ` Benjamin Herrenschmidt
2011-10-04 16:44 ` Benjamin LaHaise
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=20111005092600.36d505b2@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bcrl@kvack.org \
--cc=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mason@myri.com \
--cc=torvalds@linux-foundation.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