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]

Message-ID: <464A1D35.8030701@intel.com>
Date:	Tue, 15 May 2007 13:51:01 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Andrew Morton <akpm@...ux-foundation.org>, gregkh@...e.de
CC:	Peter Oruba <peter.oruba@....com>, cramerj@...el.com,
	john.ronciak@...el.com, jesse.brandeburg@...el.com,
	jeffrey.t.kirsher@...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

Andrew Morton wrote:
> 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?

While Jeff just Acked the changes to e1000-specific for me, I think this is a 
good approach and would appreciate it. I'll be happy to pull the change and push 
it through in due time.

Auke

-
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/