From: Don Dutile <ddutile-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>,
881731-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org
Subject: Bug#881731: rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA
Date: Tue, 14 Nov 2017 15:41:13 -0500 [thread overview]
Message-ID: <7f295a93-e27e-6661-7e57-743818e12ef5@redhat.com> (raw)
In-Reply-To: <20171114190805.GF4263-uk2M96/98Pc@public.gmane.org>
On 11/14/2017 02:08 PM, Jason Gunthorpe wrote:
>> However, it would of course be better to teach udma_barrier.h about
>> these architectures.
>
> The issue is that some architectures just can't do cache coherent DMA
> on any implementation. eg m68k
>
> There is no correct udma_barrier.h at all in those cases.
>
> We need to teach debian to follow cmake and exclude the missing
> installables in these cases..
>
> Or do not build at all on these arch's..
>
> Jason
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Jason:
Why am I being cc'd on this debian bug?
I also received a notice about a bug fix in debian, and I had zip to do with it.
Is my name tagged in Debian wrt rdma for some reason? by someone? other?
-dd
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-14 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1eFJN2-000FNY-O1@fasolo.debian.org>
[not found] ` <151067381730.19157.7563136692092597267.reportbug@ghostwheel.internal.ucko.debian.net>
2017-11-14 19:08 ` Bug#881731: rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA Jason Gunthorpe
[not found] ` <20171114190805.GF4263-uk2M96/98Pc@public.gmane.org>
2017-11-14 20:41 ` Don Dutile [this message]
[not found] ` <7f295a93-e27e-6661-7e57-743818e12ef5-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-15 5:44 ` Leon Romanovsky
[not found] ` <20171115054400.GP18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-11-15 14:50 ` Bart Van Assche
2017-11-16 12:39 ` Bug#881731: marked as done (rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA) Debian Bug Tracking System
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=7f295a93-e27e-6661-7e57-743818e12ef5@redhat.com \
--to=ddutile-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=881731-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org \
--cc=jgg-uk2M96/98Pc@public.gmane.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