From: Jeff Garzik <jeff@garzik.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [git pull] PCI fixes
Date: Fri, 06 Jun 2008 18:04:24 -0400 [thread overview]
Message-ID: <4849B468.8060903@garzik.org> (raw)
In-Reply-To: <200806061126.11037.jbarnes@virtuousgeek.org>
Jesse Barnes wrote:
> Please pull a few more fixes for 2.6.26:
> git pull git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6.git for-linus
>
> There's nothing big or critical here, just a couple of things that would be
> nice to see in 2.6.26: a fix for OLPC and a new quirk for VIA bridges.
>
> Thanks,
> Jesse
>
> Andres Salomon (1):
> PCI/x86: fix up PCI stuff so that PCI_GOANY supports OLPC
>
> Bertram Felgenhauer (1):
> x86/PCI: add workaround for bug in ASUS A7V600 BIOS (rev 1005)
>
> arch/x86/Kconfig | 11 +++++------
> arch/x86/pci/init.c | 3 ++-
> arch/x86/pci/irq.c | 7 +++++++
> arch/x86/pci/olpc.c | 5 +++--
> arch/x86/pci/pci.h | 2 +-
> 5 files changed, 18 insertions(+), 10 deletions(-)
Even though these patches have made a previous appearance on the list,
any chance you could be talked into including a summary patch, when you
push upstream? It's nice to be able to give the push one last look.
Jeff
next prev parent reply other threads:[~2008-06-06 22:04 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 18:26 [git pull] PCI fixes Jesse Barnes
2008-06-06 22:04 ` Jeff Garzik [this message]
2008-06-06 22:16 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2012-03-05 21:49 Jesse Barnes
2012-02-17 17:24 Jesse Barnes
2011-12-17 17:29 Jesse Barnes
2011-12-18 2:33 ` Yinghai Lu
2011-12-18 5:52 ` Jesse Barnes
2011-12-18 22:14 ` Linus Torvalds
2012-01-06 20:46 ` Jesse Barnes
2012-01-07 1:14 ` Yinghai Lu
2011-11-23 22:44 Jesse Barnes
2011-11-23 23:02 ` Linus Torvalds
2011-12-05 19:22 ` Jesse Barnes
2011-12-06 8:08 ` Kenji Kaneshige
2011-12-06 16:14 ` Linus Torvalds
2011-12-06 22:36 ` Yinghai Lu
2011-12-07 8:18 ` Kenji Kaneshige
2011-12-07 19:20 ` Yinghai Lu
2011-12-07 7:58 ` Kenji Kaneshige
2011-08-19 16:17 Jesse Barnes
2011-08-19 16:46 ` Greg KH
2011-08-19 17:12 ` Jesse Barnes
2011-08-19 17:19 ` Jesse Barnes
2011-06-23 20:37 Jesse Barnes
2011-06-24 15:38 ` Linus Torvalds
2011-06-24 15:53 ` Jesse Barnes
2011-06-24 16:07 ` Linus Torvalds
2011-06-24 16:11 ` Jesse Barnes
2011-06-24 22:56 ` Linus Torvalds
2011-06-25 0:00 ` Jesse Barnes
2011-06-25 0:17 ` Yinghai Lu
2011-06-28 17:02 ` Jesse Barnes
2011-06-29 1:04 ` Ram Pai
2011-03-25 17:22 Jesse Barnes
2010-12-17 23:29 Jesse Barnes
2010-11-15 17:45 Jesse Barnes
2010-11-16 11:16 ` Andreas Schwab
2010-11-16 11:23 ` Wolfram Sang
2010-11-16 17:00 ` Jesse Barnes
2010-08-31 15:49 Jesse Barnes
2010-06-09 22:53 Jesse Barnes
2010-06-09 23:14 ` Linus Torvalds
2010-06-10 0:20 ` Jesse Barnes
2010-06-11 21:02 ` Jesse Barnes
2010-06-11 21:02 ` Jesse Barnes
2010-04-29 3:14 Jesse Barnes
2010-04-23 20:37 Jesse Barnes
2010-03-26 23:33 Jesse Barnes
2010-01-29 0:25 Jesse Barnes
2010-01-07 22:34 Jesse Barnes
2009-12-28 16:10 Jesse Barnes
2009-11-11 8:12 Jesse Barnes
2009-10-12 17:32 Jesse Barnes
2009-08-10 17:30 Jesse Barnes
2009-07-06 18:00 Jesse Barnes
2009-06-06 20:32 Jesse Barnes
2009-05-15 22:09 Jesse Barnes
2009-04-27 18:54 Jesse Barnes
2009-04-07 18:00 Jesse Barnes
2009-02-26 22:24 Jesse Barnes
2009-02-26 22:36 ` Matthew Wilcox
2009-02-26 22:39 ` Jesse Barnes
2009-02-27 0:45 ` Jesse Barnes
2009-02-13 22:07 Jesse Barnes
2009-02-03 2:19 Jesse Barnes
2009-01-21 22:00 Jesse Barnes
2008-12-19 1:30 Jesse Barnes
2008-11-13 20:50 Jesse Barnes
2008-11-07 17:00 Jesse Barnes
2008-09-23 19:14 Jesse Barnes
2008-09-13 0:02 Jesse Barnes
2008-08-25 17:07 Jesse Barnes
2008-08-19 17:03 Jesse Barnes
2008-08-11 17:27 Jesse Barnes
2008-07-07 22:34 Jesse Barnes
2008-06-14 20:23 Jesse Barnes
2008-06-14 20:29 ` Rafael J. Wysocki
2008-05-27 22:55 Jesse Barnes
2008-05-20 17:51 Jesse Barnes
2008-05-13 17:42 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=4849B468.8060903@garzik.org \
--to=jeff@garzik.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.