From: Greg KH <gregkh@suse.de>
To: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
pcihpd-discuss@lists.sourceforge.net, mingo@redhat.com,
jbarnes@virtuousgeek.org
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Subject: PCI MAINTAINER change
Date: Sun, 20 Apr 2008 23:28:06 -0700 [thread overview]
Message-ID: <20080421062806.GA4919@suse.de> (raw)
In-Reply-To: <20080421062139.GA4901@suse.de>
On Sun, Apr 20, 2008 at 11:21:39PM -0700, Greg KH wrote:
> Here are a some PCI and PCI hotplug patches against your 2.6.25 git tree.
>
> They contain:
> - documentation movement into a new directory
> - pci section warning fixes
> - more generic PCI code for some arches
> - removal of the duplicated list of all PCI devices in the system
> - second go-around for the PCI ASPM code
> - various bugs and other minor stuff
> - change the PCI maintainer
I just wanted to highlight this last entry. I'm passing the PCI
subsystem maintainership on to Jesse Barnes <jbarnes@virtuousgeek.org>
I'd like to thank him for volunteering for the job, something for which
I know he is more than capable.
So those of you who have automated scripts to hit me with PCI
issues/bugs/complaints, might want to adjust them at this point in time.
Now what to do with all of this extra free time I'm going to have...
greg k-h
next prev parent reply other threads:[~2008-04-21 6:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 6:21 [GIT PATCH] PCI patches for 2.6.25-git Greg KH
2008-04-21 6:28 ` Greg KH [this message]
2008-04-21 15:55 ` PCI MAINTAINER change Jesse Barnes
2008-04-21 16:18 ` Linus Torvalds
2008-04-21 16:22 ` Ingo Molnar
2008-04-21 16:28 ` Jesse Barnes
[not found] <fa.TS+5+HinmGrscLiHGCM7C9dFSbk@ifi.uio.no>
[not found] ` <fa.EEEat9giRPyWOGUiYHgSIStt6vw@ifi.uio.no>
[not found] ` <fa.zR5oiQ1hgiLPwoqLOEK2ySOHKLA@ifi.uio.no>
[not found] ` <fa.vh1MNsau5uBs7WyWWCN0Huvxe98@ifi.uio.no>
[not found] ` <fa.JwWRxW97po7bp7uP8gASvgGakFc@ifi.uio.no>
2008-04-22 1:27 ` Robert Hancock
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=20080421062806.GA4919@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mingo@redhat.com \
--cc=pcihpd-discuss@lists.sourceforge.net \
--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 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.