From: Greg KH <gregkh@suse.de>
To: "Yeisley, Dan P." <dan.yeisley@unisys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.14.2 Support for 1K I/O space granularity on the Intel P64H2
Date: Wed, 23 Nov 2005 10:18:27 -0800 [thread overview]
Message-ID: <20051123181827.GA27403@suse.de> (raw)
In-Reply-To: <94C8C9E8B25F564F95185BDA64AB05F6028E115E@USTR-EXCH5.na.uis.unisys.com>
On Wed, Nov 23, 2005 at 01:02:52PM -0500, Yeisley, Dan P. wrote:
> The Intel P64H2 PCI bridge has the ability to allocate I/O space with
> 1KB granularity. I've written a patch against 2.6.14.2 to take
> advantage of this option. I've tested it on the latest Unisys
> ES7000-600.
Shouldn't this be made into a pci quirk somehow?
> linux-2.6.14.2-en1k/drivers/pci/probe.c
> --- linux-2.6.14.2/drivers/pci/probe.c 2005-11-11 00:33:12.000000000
> -0500
Your patch is linewrapped and can't be applied :(
thanks,
greg k-h
next prev parent reply other threads:[~2005-11-23 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 18:02 [PATCH] 2.6.14.2 Support for 1K I/O space granularity on the Intel P64H2 Yeisley, Dan P.
2005-11-23 18:18 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-23 18:57 Yeisley, Dan P.
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=20051123181827.GA27403@suse.de \
--to=gregkh@suse.de \
--cc=dan.yeisley@unisys.com \
--cc=linux-kernel@vger.kernel.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