linux-kernel - Re: [PATCH 0/2] PCI-X/PCI-Express read control interfaces

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 16 May 2007 13:05:51 +0200
From:	"Peter Oruba" <peter.oruba@....com>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
cc:	gregkh@...e.de, cramerj@...el.com, john.ronciak@...el.com,
	jesse.brandeburg@...el.com, jeffrey.t.kirsher@...el.com,
	auke-jan.h.kok@...el.com, rolandd@...co.com, halr@...taire.com,
	linux-driver@...gic.com,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Stephen Hemminger" <shemminger@...ux-foundation.org>
Subject: Re: [PATCH 0/2] PCI-X/PCI-Express read control interfaces

Am Dienstag, 15. Mai 2007 21:37:21 schrieb Andrew Morton:
> On Tue, 15 May 2007 13:50:27 +0200
>
> "Peter Oruba" <peter.oruba@....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?

I cannot tell how common AM8131 based systems in combination with one of these 
three devices actually are. However, this patch set is essential for those 
systems.


-- 
AMD Saxony Limited Liability Company & Co. KG
Operating System Research Center
Wilschdorfer Landstr. 101, 01109 Dresden, Germany
Register Court Dresden: HRA 4896
General Partner authorized to represent:
AMD Saxony LLC (Wilmington, Delaware, US)
General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/