From: Greg KH <greg@kroah.com>
To: "Lee, Jung-Ik" <jung-ik.lee@intel.com>
Cc: "'linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: Re: RFC: bare pci configuration access functions ?
Date: Thu, 31 Oct 2002 21:38:42 -0800 [thread overview]
Message-ID: <20021101053841.GE13031@kroah.com> (raw)
In-Reply-To: <72B3FD82E303D611BD0100508BB29735046DFF6E@orsmsx102.jf.intel.com>
On Thu, Oct 31, 2002 at 08:52:24PM -0800, Lee, Jung-Ik wrote:
> Minor fix to the code.
> A patch to a flying patch ;-)
Ok, maybe just because I've eaten too much candy tonight, but I do not
understand where you are trying to go with this odd pseudo code.
What's wrong with the _existing_ pci_config_read() and
pci_config_write() function pointers that ia64 and i386 have? Can't you
just look into if the other archs can set them to the proper function in
their pci init functions too?
thanks,
greg k-h
next prev parent reply other threads:[~2002-11-01 5:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 4:52 RFC: bare pci configuration access functions ? Lee, Jung-Ik
2002-11-01 5:38 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-04 22:30 Lee, Jung-Ik
2002-11-04 20:17 Lee, Jung-Ik
2002-11-04 21:30 ` Greg KH
2002-11-01 4:45 Lee, Jung-Ik
2002-11-01 2:39 Lee, Jung-Ik
2002-11-01 2:48 ` Greg KH
2002-10-31 19:29 Lee, Jung-Ik
2002-11-01 1:02 ` Greg KH
2002-11-01 1:55 ` Lee, Jung-Ik
2002-11-01 2:11 ` Greg KH
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=20021101053841.GE13031@kroah.com \
--to=greg@kroah.com \
--cc=jung-ik.lee@intel.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