From: "David S. Miller" <davem@davemloft.net>
To: habeck@sgi.com
Cc: steiner@sgi.com, linux-kernel@vger.kernel.org,
tony.luck@gmail.com, linville@tuxdriver.com
Subject: Re: 2.6.14-rc1 breaks tg3 on ia64
Date: Mon, 19 Sep 2005 18:14:51 -0700 (PDT) [thread overview]
Message-ID: <20050919.181451.128902094.davem@davemloft.net> (raw)
In-Reply-To: <432F3F11.69973A36@sgi.com>
From: Mike Habeck <habeck@sgi.com>
Date: Mon, 19 Sep 2005 17:43:29 -0500
> So is hacking the SN specific code to initialize the device's
> state to PCI_DO more attractive than keeping John Linville current
> patch? As I said, I personally see nothing wrong with John
> Linville current patch to check the actual state of the device.
I think keeping John's patch in is fine, especially if you guys
do have the longer term strategy of making pci_resource_to_bus()
work properly on this platform. Because somewhere down the line
something else will depend upon it being correct, and you'll
need to address this properly.
Actually, some PCI quirk fixups use pcibios_bus_to_resource(), but the
one's that do this are probably not relevant on ia64.
next prev parent reply other threads:[~2005-09-20 1:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050919204523.GD15838@sgi.com>
2005-09-19 22:43 ` Mike Habeck
2005-09-20 1:14 ` David S. Miller [this message]
2005-09-13 5:22 Keith Owens
2005-09-13 5:37 ` David S. Miller
2005-09-13 6:17 ` Keith Owens
2005-09-13 6:47 ` David S. Miller
2005-09-13 6:48 ` Keith Owens
2005-09-13 6:59 ` Greg KH
2005-09-13 7:27 ` Keith Owens
2005-09-17 15:47 ` Tony Luck
2005-09-17 15:59 ` John W. Linville
2005-09-17 16:16 ` Greg KH
2005-09-17 16:34 ` Jack Steiner
2005-09-17 16:48 ` John W. Linville
2005-09-17 16:46 ` John W. Linville
2005-09-18 6:23 ` David S. Miller
2005-09-18 6:33 ` Tony Luck
2005-09-18 11:44 ` Jack Steiner
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=20050919.181451.128902094.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=habeck@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=steiner@sgi.com \
--cc=tony.luck@gmail.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
all inboxes | Powered by JetHome®