From: David Marchand <david.marchand@redhat.com>
To: Raslan Darawsheh <rasland@mellanox.com>
Cc: Ali Alnubani <alialnu@mellanox.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Suanming Mou <suanmingm@mellanox.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] common/mlx5: fix mlx5 build
Date: Mon, 20 Jul 2020 14:23:44 +0200 [thread overview]
Message-ID: <CAJFAV8yYr0pOkyek_8U_8gcnuw6g_mFz0-VS_F=ygk=a5YcOBQ@mail.gmail.com> (raw)
In-Reply-To: <AM0PR05MB67079F4469EED5BE5CDC9CDCC27B0@AM0PR05MB6707.eurprd05.prod.outlook.com>
On Mon, Jul 20, 2020 at 10:59 AM Raslan Darawsheh <rasland@mellanox.com> wrote:
> > > Yes I noticed it already,
> > > but it's coming from the fact that it's trying to apply it on a tree that doesn't
> > have the patch which this patch is trying to fix.
> > >
> > > ../drivers/common/mlx5/linux/mlx5_glue.c:19:10: fatal error:
> > '../mlx5_malloc.h' file not found
> > > #include "../mlx5_malloc.h"
> > > ^~~~~~~~~~~~~~~~~~
> >
> > Ok, I see.
> > Too bad the robot is not testing on the right branch.
> Yes I agree and I guess we need to fix that, who can help with this?
Afaik, anyone can fix it.
The robot scripts initiated by Aaron are on github:
https://github.com/orgcandman/pw-ci
--
David Marchand
prev parent reply other threads:[~2020-07-20 12:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 11:51 Ali Alnubani
2020-07-19 15:17 ` Raslan Darawsheh
2020-07-20 8:24 ` David Marchand
2020-07-20 8:38 ` Raslan Darawsheh
2020-07-20 8:51 ` David Marchand
2020-07-20 8:59 ` Raslan Darawsheh
2020-07-20 12:23 ` David Marchand [this message]
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='CAJFAV8yYr0pOkyek_8U_8gcnuw6g_mFz0-VS_F=ygk=a5YcOBQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=alialnu@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=rasland@mellanox.com \
--cc=suanmingm@mellanox.com \
--cc=thomas@monjalon.net \
/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).