From: Andrew Morton <akpm@linux-foundation.org>
To: Eric Anholt <eric@anholt.net>
Cc: penberg@cs.helsinki.fi, elendil@planet.nl,
linux-kernel@vger.kernel.org, apw@canonical.com,
colin.king@canonical.com, tim.gardner@canonicalc.com,
bjorn.helgaas@hp.com
Subject: Re: [PATCH 2/2] pnp: add PNP resource range checking function
Date: Tue, 9 Jun 2009 15:09:44 -0700 [thread overview]
Message-ID: <20090609150944.6ffa8038.akpm@linux-foundation.org> (raw)
In-Reply-To: <1244508839.7564.0.camel@gaiman.anholt.net>
On Mon, 08 Jun 2009 17:53:59 -0700
Eric Anholt <eric@anholt.net> wrote:
> On Sat, 2009-06-06 at 10:28 +0300, Pekka Enberg wrote:
> > Hi Frans,
> >
> > Frans Pop wrote:
> > >> Add a PNP resource range check function, indicating whether a resource
> > >> has been assigned to any device.
> > >
> > > Shouldn't this patch come *before* your patch 1/2?
> > > You now seem to use this function in a commit where it has not yet been
> > > defined, which could result in build errors during bisections.
> >
> > Yes, correct. Sorry about that!
> >
> > Pekka
>
> This is already in drm-intel-next
>
Neither patch is in linux-next. So either a) drm-intel-next contains
2.6.31 material or b) your processes broke.
Either way, these patches fix a "serious performance regression". They
should be merged into 2.6.30 or 2.6.30.x, shouldn't they?
next prev parent reply other threads:[~2009-06-09 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 6:36 Pekka J Enberg
2009-06-06 7:31 ` Frans Pop
2009-06-06 7:28 ` Pekka Enberg
2009-06-09 0:53 ` Eric Anholt
2009-06-09 22:09 ` Andrew Morton [this message]
2009-06-11 20:33 ` 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=20090609150944.6ffa8038.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=bjorn.helgaas@hp.com \
--cc=colin.king@canonical.com \
--cc=elendil@planet.nl \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=tim.gardner@canonicalc.com \
/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
all inboxes | Powered by JetHome®