From: Michael Ellerman <michael@ellerman.id.au>
To: Robert Walsh <rjwalsh@pathscale.com>
Cc: support@pathscale.com, Andrew Morton <akpm@osdl.org>,
openib-general <openib-general@openib.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [openib-general] Can't build drivers/infiniband/hw/ipath/ipath_keys.c on arch/powerpc
Date: Mon, 06 Nov 2006 19:31:22 +1100 [thread overview]
Message-ID: <1162801882.8175.42.camel@localhost.localdomain> (raw)
In-Reply-To: <454EE778.2030109@pathscale.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Sun, 2006-11-05 at 23:42 -0800, Robert Walsh wrote:
> Michael Ellerman wrote:
> > Hi,
> >
> > Just a heads-up, drivers/infiniband/hw/ipath/ipath_keys.c doesn't build
> > on powerpc because we have don't have bus_to_virt().
> >
> > (Actually you can't select CONFIG_INFINIBAND_IPATH on mainline because
> > powerpc doesn't enable PCI_MSI, but we will real soon now, and when we
> > do this will start breaking people's all modconfig builds).
>
> Thanks for the heads-up. We're working to remove this requirement as we
> speak.
Sweet.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-11-06 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 7:33 Can't build drivers/infiniband/hw/ipath/ipath_keys.c on arch/powerpc Michael Ellerman
2006-11-06 7:42 ` [openib-general] " Robert Walsh
2006-11-06 8:31 ` Michael Ellerman [this message]
2006-11-06 8:06 ` Benjamin Herrenschmidt
2006-11-06 16:52 ` Roland Dreier
2006-11-06 20:24 ` Benjamin Herrenschmidt
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=1162801882.8175.42.camel@localhost.localdomain \
--to=michael@ellerman.id.au \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=openib-general@openib.org \
--cc=rjwalsh@pathscale.com \
--cc=support@pathscale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.