From: Matthew Wilcox <matthew@wil.cx>
To: "Zhao, Yu" <yu.zhao@intel.com>
Cc: linux-kernel@vger.kernel.org, eric@anholt.net,
Matthew Wilcox <willy@linux.intel.com>,
jbarnes@virtuousgeek.org
Subject: Re: [PATCH 3/3] PCI: Add pci_read_base() API
Date: Mon, 28 Jul 2008 19:49:31 -0600 [thread overview]
Message-ID: <20080729014931.GB28989@parisc-linux.org> (raw)
In-Reply-To: <7A25B56E4BE99C4283EB931CD1A40E1101586F18@pdsmsx414.ccr.corp.intel.com>
On Tue, Jul 29, 2008 at 09:22:03AM +0800, Zhao, Yu wrote:
> Greetings,
>
> It would be nice if people can have an enhanced pci_update_resource to update non-standard BARs probed by pci_read_base.
Yes, that would be a natural addition to the API. However, we don't
tend to add APIs until we have a use case for them. Do you have
anything in the pipeline that could use this feature? I'm quite happy
to write the code for you if you do.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-07-29 1:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 17:38 pci_read_base patch series Matthew Wilcox
2008-07-28 17:38 ` [PATCH 1/3] Rewrite PCI BAR reading code Matthew Wilcox
2008-07-28 17:39 ` [PATCH 2/3] PCI: Handle 64-bit resources better on 32-bit machines Matthew Wilcox
2008-07-28 21:30 ` Jesse Barnes
2008-07-29 0:46 ` Matthew Wilcox
2008-07-28 17:39 ` [PATCH 3/3] PCI: Add pci_read_base() API Matthew Wilcox
2008-07-29 1:22 ` Zhao, Yu
2008-07-29 1:49 ` Matthew Wilcox [this message]
2008-07-29 2:36 ` Zhao, Yu
2008-08-04 6:38 ` Grant Grundler
2008-08-06 14:38 ` Matthew Wilcox
2008-08-10 0:47 ` Grant Grundler
2008-08-10 1:01 ` Matthew Wilcox
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=20080729014931.GB28989@parisc-linux.org \
--to=matthew@wil.cx \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@linux.intel.com \
--cc=yu.zhao@intel.com \
/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