From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: David Marchand <david.marchand@redhat.com>,
"Xia, Chenbo" <chenbo.xia@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Liu, Changpeng" <changpeng.liu@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Aaron Conole <aconole@redhat.com>, dpdklab <dpdklab@iol.unh.edu>,
ci@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] vhost: rename driver callbacks struct
Date: Wed, 3 Nov 2021 10:52:51 +0100 [thread overview]
Message-ID: <242aa665-45b6-2441-4288-26a4056dc3e2@redhat.com> (raw)
In-Reply-To: <3a63bda9-2ff7-30bc-87b7-48e1324d1666@redhat.com>
On 11/3/21 09:38, Maxime Coquelin wrote:
> Hi David,
>
> On 11/3/21 09:36, David Marchand wrote:
>> On Wed, Nov 3, 2021 at 9:16 AM Xia, Chenbo <chenbo.xia@intel.com> wrote:
>>> Testing issues reported in patchwork is expected as SPDK uses
>>> this struct, so we can ignore it as SPDK will rename it when it
>>> adapts to DPDK 21.11
>>
>> Please, no.
>> We can't simply say "ignore failure in CI".
>>
>> The SPDK build test must be disabled in CI first.
>> You can create a bugzilla and assign it to UNH lab.
>> Example: https://bugs.dpdk.org/show_bug.cgi?id=579
>>
>> Once done, we can merge this patch in DPDK.
>>
>>
>> In parallel, either prepare the patch or talk to SPDK guys to handle
>> this change.
>> Once this is done, update the bugzilla so that we can get SPDK build
>> tested again in CI.
>
> Thanks for the insights, I'll file a Bz and work with the SPDK team.
The Bz has been filed:
https://bugs.dpdk.org/show_bug.cgi?id=876
> Maxime
>> Thanks.
>>
>>
next prev parent reply other threads:[~2021-11-03 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 10:47 Maxime Coquelin
2021-11-03 8:16 ` Xia, Chenbo
2021-11-03 8:36 ` David Marchand
2021-11-03 8:38 ` Maxime Coquelin
2021-11-03 9:52 ` Maxime Coquelin [this message]
2021-11-03 13:11 ` [dpdk-dev] [dpdklab] " Lincoln Lavoie
2021-11-03 13:16 ` Maxime Coquelin
2021-11-03 14:38 ` Lincoln Lavoie
2021-11-03 9:10 ` [dpdk-dev] " Xia, Chenbo
2021-11-04 2:48 ` Liu, Changpeng
2021-11-03 13:46 ` Maxime Coquelin
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=242aa665-45b6-2441-4288-26a4056dc3e2@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=aconole@redhat.com \
--cc=changpeng.liu@intel.com \
--cc=chenbo.xia@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--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).