From: David Marchand <david.marchand@redhat.com>
To: "Szwed, Maciej" <maciej.szwed@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
Jeff Guo <jia.guo@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] |FAILURE| pw97277 [PATCH] [v4] eal: read data buffer on RTE_INTR_HANDLE_VFIO_REQ
Date: Fri, 3 Sep 2021 14:00:54 +0200 [thread overview]
Message-ID: <CAJFAV8xR92xKzup-D9bouGXe1G3FTpTv0yHajmDKHngLgDj_pA@mail.gmail.com> (raw)
In-Reply-To: <BL0PR11MB2948145FF1F1FC88F30D6F9897CF9@BL0PR11MB2948.namprd11.prod.outlook.com>
On Fri, Sep 3, 2021 at 10:59 AM Szwed, Maciej <maciej.szwed@intel.com> wrote:
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Szwed, Maciej
> Sent: Monday, August 30, 2021 11:34 AM
> To: dev@dpdk.org
> Subject: Re: [dpdk-dev] |FAILURE| pw97277 [PATCH] [v4] eal: read data buffer on RTE_INTR_HANDLE_VFIO_REQ
>
> Hi,
> I'm new to posting patches to DPDK repository. I've submitted a patch recently and one of the tests performed on it failed. I went through the failed test log and it looks like it does not have anything to do with my patch. You can check details below. What should be the next steps I should perform?
>
About this specific failure in the CI, this is a known issue.
This failure here won't block acceptance of this patch.
But we need a review/ack for this patch.
When submitting a patch, you should copy maintainers and people who
worked on this part of DPDK.
Anatoly, Jeff, can you have a look?
Thanks.
--
David Marchand
next prev parent reply other threads:[~2021-09-03 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210825205901.594F789060@noxus.dpdklab.iol.unh.edu>
2021-08-30 9:34 ` Szwed, Maciej
2021-09-03 8:59 ` Szwed, Maciej
2021-09-03 12:00 ` David Marchand [this message]
2021-09-21 11:23 ` Szwed, Maciej
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=CAJFAV8xR92xKzup-D9bouGXe1G3FTpTv0yHajmDKHngLgDj_pA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=jia.guo@intel.com \
--cc=maciej.szwed@intel.com \
/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).