From: Ingo Molnar <mingo@elte.hu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
Yinghai Lu <yhlu.kernel.send@gmail.com>,
Dave Jones <davej@redhat.com>
Subject: Re: [git pull] PCI updates for 2.6.26
Date: Tue, 6 May 2008 18:58:02 +0200 [thread overview]
Message-ID: <20080506165802.GB7801@elte.hu> (raw)
In-Reply-To: <200805050945.39298.jbarnes@virtuousgeek.org>
* Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Tuesday, April 29, 2008 2:09 pm Ingo Molnar wrote:
> > * Ingo Molnar <mingo@elte.hu> wrote:
> > > there are a few other PCI items in x86.git btw that you might want to
> > > have a look at and which you might want to pick up into your tree -
> > > they dont really belong into x86.git.
> >
> > there's some PCI impact in the "x86 GART" topic tree below, could you
> > have a look whether you can see anything objectionable:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-x86-gart.git
> > for-linus
> >
> > if not we'd like to send this to Linus - those changes are stable and
> > tested.
>
> Not sure I'm the right person to look at these, but they seem fine to
> me.
was trolling for some extra review - the code _does_ touch a tiny bit of
PCI code after all ;) Anyway, it's now delayed to v2.6.27, so if there's
any problem with it we'll see it in linux-next/mm.
Ingo
next prev parent reply other threads:[~2008-05-06 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 17:12 [git pull] PCI updates for 2.6.26 Jesse Barnes
2008-04-29 20:26 ` Ingo Molnar
2008-04-29 21:09 ` Ingo Molnar
2008-05-05 16:45 ` Jesse Barnes
2008-05-06 16:58 ` Ingo Molnar [this message]
2008-04-29 21:32 ` 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=20080506165802.GB7801@elte.hu \
--to=mingo@elte.hu \
--cc=davej@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=torvalds@linux-foundation.org \
--cc=yhlu.kernel.send@gmail.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