From: Andrew Morton <akpm@linux-foundation.org>
To: "Peter Oruba" <peter.oruba@amd.com>
Cc: gregkh@suse.de, cramerj@intel.com, john.ronciak@intel.com,
jesse.brandeburg@intel.com, jeffrey.t.kirsher@intel.com,
auke-jan.h.kok@intel.com, rolandd@cisco.com, halr@voltaire.com,
linux-driver@qlogic.com,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Stephen Hemminger" <shemminger@linux-foundation.org>
Subject: Re: [PATCH 0/2] PCI-X/PCI-Express read control interfaces
Date: Tue, 15 May 2007 12:37:21 -0700 [thread overview]
Message-ID: <20070515123721.1bfb02a3.akpm@linux-foundation.org> (raw)
In-Reply-To: <200705151350.28330.peter.oruba@amd.com>
On Tue, 15 May 2007 13:50:27 +0200
"Peter Oruba" <peter.oruba@amd.com> wrote:
> This patch set introduces a PCI-X / PCI-Express read byte count control
> interface. Instead of letting every driver to directly read/write to PCI
> config space for that, an interface is provided. The interface functions then
> can be used for quirks since some PCI bridges require that read byte count
> values are set by the BIOS and left unchanged by device drivers.
Some of the patches were wordwrapped, which I fixed.
The way we would merge a feature like this is
- get maintainers to review-and-ack the change
- merge the core patch into Greg's PCI tree and later into
mainline.
- Once the base infrastructure is in mainline, feed the per-driver
changes into the tree via the appropriate maintainers.
This takes, umm, months and consumes quite a bit of my time. I'm becoming
inclined just to slam stuff like this straight in as you've proposed, but
for now, let's play the game - I split the patches up appropriately. I
don't think there's any particular urgency behind this, is there?
next prev parent reply other threads:[~2007-05-15 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 11:50 [PATCH 0/2] PCI-X/PCI-Express read control interfaces Peter Oruba
2007-05-15 11:59 ` [PATCH 1/2] " Peter Oruba
2007-05-16 17:10 ` Randy Dunlap
2007-05-15 12:03 ` [PATCH 2/2] " Peter Oruba
2007-05-15 20:32 ` Jeff Kirsher
2007-05-15 19:37 ` Andrew Morton [this message]
2007-05-15 20:51 ` [PATCH 0/2] " Kok, Auke
2007-05-15 21:35 ` Andrew Vasquez
2007-05-16 14:39 ` [PATCH 0/2] PCI-X/PCI-Express read control interfaces - Patch correction Peter Oruba
2007-05-16 11:05 ` [PATCH 0/2] PCI-X/PCI-Express read control interfaces Peter Oruba
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=20070515123721.1bfb02a3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=auke-jan.h.kok@intel.com \
--cc=cramerj@intel.com \
--cc=gregkh@suse.de \
--cc=halr@voltaire.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-driver@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.oruba@amd.com \
--cc=rolandd@cisco.com \
--cc=shemminger@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox