From: Dave Olson <dave.olson@qlogic.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Ralph Campbell <ralph.campbell@qlogic.com>,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, general@lists.openfabrics.org
Subject: Re: [ofa-general] Re: [GIT PULL] please pull infiniband.git
Date: Sat, 19 Apr 2008 08:20:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.00.0804190817280.21302@topaz.pathscale.com> (raw)
In-Reply-To: <adaod86aq9j.fsf@cisco.com>
On Sat, 19 Apr 2008, Roland Dreier wrote:
| > drivers/built-in.o: In function `ipath_init_one':
| > ipath_driver.c:(.devinit.text+0x1e5bc): undefined reference to `ipath_init_iba7220_funcs'
Yes, that issue should be fixed. Our preference was to not build
if it wouldn't work. We'd have to add the conditional check at
the function setup routines.
| I also removed the dependency on HT_IRQ || PCI_MSI in the Kconfig, since
| the iba7220 support should work without it. I know we discussed this
| before, but looking closer at the code, the dependency seems pointless
| to me, since it's still possible to build a driver that doesn't work if
| a particular system needs, say HT_IRQ, and the user selects PCI_MSI.
| And since iba7220 doesn't need either, we might as well let people build
| that.
|
| If this is OK with everyone, I will merge this with a proper changelog.
At this point, I guess I'd agree. We've added checks for "no interrupt"
after the driver is loaded, so I guess that covers the issue well
enough.
Dave Olson
dave.olson@qlogic.com
next prev parent reply other threads:[~2008-04-19 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 14:53 [GIT PULL] please pull infiniband.git Roland Dreier
2008-04-19 8:16 ` Ingo Molnar
2008-04-19 14:11 ` [ofa-general] " Roland Dreier
2008-04-19 14:18 ` Roland Dreier
2008-04-19 15:20 ` Dave Olson [this message]
2008-04-19 16:12 ` Roland Dreier
2008-04-20 14:47 ` Dave Olson
2008-04-21 1:55 ` Roland Dreier
2008-04-21 2:35 ` Dave Olson
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=alpine.LFD.1.00.0804190817280.21302@topaz.pathscale.com \
--to=dave.olson@qlogic.com \
--cc=akpm@linux-foundation.org \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ralph.campbell@qlogic.com \
--cc=rdreier@cisco.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).