linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: torvalds@osdl.org, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [BK PATCH] PCI patches for 2.6.10-rc2
Date: Mon, 10 Jan 2005 09:18:27 -0800	[thread overview]
Message-ID: <20050110171827.GA30296@kroah.com> (raw)

Hi,

Here are some PCI and PCI Hotplug patches for 2.6.10.  All of these have
been in the past few -mm releases.

Highlights include:
	- start of typesafe pci power states
	- loads of little bug fixes.

Please pull from:
	bk://kernel.bkbits.net/gregkh/linux/pci-2.6

thanks,

greg k-h

p.s. I'll send these as patches in response to this email to lkml for
those who want to see them.


 MAINTAINERS                            |   44 +
 arch/i386/pci/fixup.c                  |    4 
 arch/i386/pci/irq.c                    |    8 
 arch/i386/pci/pci.h                    |    2 
 drivers/media/video/bttv-driver.c      |   10 
 drivers/net/3c59x.c                    |   16 
 drivers/net/8139cp.c                   |   12 
 drivers/net/8139too.c                  |    5 
 drivers/net/amd8111e.c                 |   32 -
 drivers/net/e100.c                     |    8 
 drivers/net/eepro100.c                 |   16 
 drivers/net/pci-skeleton.c             |    4 
 drivers/net/sis900.c                   |   14 
 drivers/net/starfire.c                 |    4 
 drivers/net/typhoon.c                  |    9 
 drivers/net/via-rhine.c                |    4 
 drivers/net/via-velocity.c             |   64 +-
 drivers/pci/hotplug/acpiphp_ibm.c      |    2 
 drivers/pci/hotplug/cpci_hotplug_pci.c |    2 
 drivers/pci/hotplug/cpcihp_generic.c   |    2 
 drivers/pci/hotplug/cpqphp_pci.c       |   30 -
 drivers/pci/hotplug/fakephp.c          |    2 
 drivers/pci/hotplug/ibmphp.h           |    2 
 drivers/pci/hotplug/ibmphp_core.c      |  830 +++++++++++++++++----------------
 drivers/pci/hotplug/ibmphp_pci.c       |   56 +-
 drivers/pci/hotplug/shpchp.h           |    2 
 drivers/pci/pci.c                      |   67 ++
 drivers/pci/probe.c                    |   56 ++
 drivers/pci/quirks.c                   |   14 
 drivers/pci/setup-bus.c                |    9 
 drivers/pci/setup-irq.c                |    3 
 include/linux/pci.h                    |   34 +
 32 files changed, 807 insertions(+), 560 deletions(-)
-----

<macro:mips.com>:
  o PCI: PCI early fixup missing bits

Adrian Bunk:
  o PCI Hotplug: drivers/pci/hotplug/ : simply use MODULE
  o PCI: arch/i386/pci/: make some code static

David Howells:
  o PCI: Make pci_set_power_state() check register version

Domen Puncer:
  o hotplug/acpiphp_ibm: module_param fix

Greg Kroah-Hartman:
  o PCI Hotplug: remove my old email address
  o PCI: fix bttv-driver "cleanup" that called an incorrect function
  o PCI: fix typo on previous pci_set_power_state() patch for hte sis900 driver
  o PCI: fix up function calls for CONFIG_PCI=N

Maciej W. Rozycki:
  o PCI: Don't touch BARs of host bridges

Matthew Wilcox:
  o PCI: Software visible configuration request retry status
  o PCI: cope with duplicate bus numbers better

Pavel Machek:
  o PCI: fix sparse warnings in drivers/net/* and bttv
  o PCI: clean up state usage in pci core
  o PCI: add prototype for pci_choose_state()
  o PCI: add pci_choose_state()
  o PCI: Cleanup PCI power states

Randy Dunlap:
  o cpqphp: reduce stack usage

Rolf Eike Beer:
  o PCI Hotplug: don't check pointer before kalling kfree in ibmphp_pci.c
  o PCI Hotplug: use PCI_DEVFN in ibmphp_pci.c
  o PCI Hotplug: Remove unneeded kmalloc casts from ibmphp_pci.c
  o PCI Hotplug: ibmphp_core.c: useless casts
  o PCI Hotplug: ibmphp_core.c: coding style

Thomas Gleixner:
  o PCI: Fix debug statement


             reply	other threads:[~2005-01-10 17:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 17:18 Greg KH [this message]
2005-01-10 17:19 ` [BK PATCH] PCI patches for 2.6.10-rc2 Greg KH
2005-01-10 17:20 ` [PATCH] PCI patches for 2.6.10 Greg KH
2005-01-10 17:20   ` Greg KH
2005-01-10 17:20     ` Greg KH
2005-01-10 17:20       ` Greg KH
2005-01-10 17:20         ` Greg KH
2005-01-10 17:20           ` Greg KH
2005-01-10 17:20             ` Greg KH
2005-01-10 17:20               ` Greg KH
2005-01-10 17:20                 ` Greg KH
2005-01-10 17:20                   ` Greg KH
2005-01-10 17:20                     ` Greg KH
2005-01-10 17:20                       ` Greg KH
2005-01-10 17:20                         ` Greg KH
2005-01-10 17:20                           ` Greg KH
2005-01-10 17:20                             ` Greg KH
2005-01-10 17:20                               ` Greg KH
2005-01-10 17:20                                 ` Greg KH
2005-01-10 17:20                                   ` Greg KH
2005-01-10 17:20                                     ` Greg KH
2005-01-10 17:20                                       ` Greg KH
2005-01-10 17:20                                         ` Greg KH
2005-01-10 17:20                                           ` Greg KH
2005-01-10 17:20                                             ` Greg KH
2005-01-10 17:20                                               ` Greg KH
2005-01-11 22:39   ` Matt Mackall
2005-01-11 22:44     ` Greg KH
2005-01-12 13:09       ` Domen Puncer

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=20050110171827.GA30296@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).