From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Don Dutile <ddutile-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
881731-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org
Cc: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Subject: Bug#881731: rdma-core: FTBFS on armhf and mips*: missing providers that need coherent DMA
Date: Wed, 15 Nov 2017 07:44:00 +0200 [thread overview]
Message-ID: <20171115054400.GP18825@mtr-leonro.local> (raw)
In-Reply-To: <7f295a93-e27e-6661-7e57-743818e12ef5-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]
On Tue, Nov 14, 2017 at 03:41:13PM -0500, Don Dutile wrote:
> 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?
Don,
All of us received this email [1], because maintainer of rdma-core package
is mailing list:
"Package: src:rdma-core; Maintainer for src:rdma-core is Linux RDMA
Mailing List <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>;"
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881731
Thanks
>
> -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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-15 5:44 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
[not found] ` <7f295a93-e27e-6661-7e57-743818e12ef5-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-15 5:44 ` Leon Romanovsky [this message]
[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=20171115054400.GP18825@mtr-leonro.local \
--to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=881731-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org \
--cc=ddutile-H+wXaHxf7aLQT0dZR+AlfA@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