From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
dev@dpdk.org, David Marchand <david.marchand@redhat.com>,
ci@dpdk.org
Subject: Re: [dpdk-ci] [dpdk-dev] [PATCH v8 1/8] net/dpaa: add support for fmlib in dpdk
Date: Wed, 9 Sep 2020 12:16:01 +0100 [thread overview]
Message-ID: <ed736224-b13e-cc90-ecfe-50a420d62770@intel.com> (raw)
In-Reply-To: <3b895652-bf88-135e-e44f-1474ccaaee40@intel.com>
On 9/8/2020 1:10 PM, Ferruh Yigit wrote:
> On 9/8/2020 11:19 AM, Thomas Monjalon wrote:
>> 08/09/2020 11:55, Ferruh Yigit:
>>> On 9/4/2020 1:51 PM, Ferruh Yigit wrote:
>>>> Series applied to dpdk-next-net/main, thanks.
>>>
>>> Hi Hemant,
>>>
>>> I need to drop the series from next-net, since new files doesn't have the
>>> Makefile support, they are causing build error for Make and affecting CI result
>>> for some new patches.
>>>
>>> I will add them back when Make support removed from the main repo.
>>
>> Make is already removed.
>
> Yes indeed, it is removed this morning, I will rebase the next-net and merge the
> patchset on top of it back.
>
patchset merged back to next-net.
>>
>> Which CI is broken?
>> Make should not be tested anymore as requested in this ticket:
>> https://bugs.dpdk.org/show_bug.cgi?id=534
>>
>>
>
> I received build error reports, they might be internal.
>
prev parent reply other threads:[~2020-09-09 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200904082921.17400-1-hemant.agrawal@nxp.com>
[not found] ` <ce4ac8e3-41bd-7d91-13ff-b40f81ae479f@intel.com>
[not found] ` <cc127313-c80c-2cab-2667-62c69d5c5f88@intel.com>
2020-09-08 10:19 ` Thomas Monjalon
2020-09-08 12:10 ` Ferruh Yigit
2020-09-09 11:16 ` Ferruh Yigit [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=ed736224-b13e-cc90-ecfe-50a420d62770@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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).