DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Supriya Shekhar Mane <sm.supriya@globaledgesoft.com>
Cc: dev <dev@dpdk.org>, Zaheer R M <zaheer.rm@globaledgesoft.com>,
	 Chandrakant Sharpa <s.chandrakant@globaledgesoft.com>,
	 Gurusidhesh G H <gurusidhesh.gh@globaledgesoft.com>
Subject: Re: [dpdk-dev] Regarding Armv7 support in DPDK-21.05
Date: Fri, 18 Jun 2021 10:33:41 +0200	[thread overview]
Message-ID: <CAJFAV8yOmp_aH6Ovqchds7bAoK-9WweEMJTux7Wn8koEWudR4w@mail.gmail.com> (raw)
In-Reply-To: <CAEmSBmaenD9T1+cgVRfbxrJJcOouX=pdD_6hSa7wFbgDuEez+Q@mail.gmail.com>

Hello Supriya,

I waived 2/3 mails from you in the ml moderation list.
Please register to the dev@ mailing list if you wish to contribute to
the project.


On Fri, Jun 18, 2021 at 10:27 AM Supriya Shekhar Mane
<sm.supriya@globaledgesoft.com> wrote:
>
> Hi Thomas,
>
> The checklist shows a functional test error(as shown in attachment),
> but the error is in X86,
> how to reproduce and fix this issue?

In this specific case, those failures come from CI issues itself.
You can ignore them.


>
> Regards,
> Supriya Mane
>
> --
> Disclaimer:This message is intended only for the designated recipient(s).
> It may contain confidential or proprietary information and may be subject
> to other confidentiality protections. If you are not a designated
> recipient, you may not review, copy or distribute this message. Please
> notify the sender by e-mail and delete this message. GlobalEdge does not
> accept any liability for virus infected mails.

This trailer does not make sense on a public mailing list.
Please ask your IT to remove it.


Thanks!

-- 
David Marchand


      reply	other threads:[~2021-06-18  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  6:28 Supriya Shekhar Mane
2021-06-18  8:33 ` 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=CAJFAV8yOmp_aH6Ovqchds7bAoK-9WweEMJTux7Wn8koEWudR4w@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gurusidhesh.gh@globaledgesoft.com \
    --cc=s.chandrakant@globaledgesoft.com \
    --cc=sm.supriya@globaledgesoft.com \
    --cc=zaheer.rm@globaledgesoft.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).