From: David Marchand <david.marchand@redhat.com>
To: Li Han <han.li1@zte.com.cn>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev <dev@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] lib/librte_eal/linuxapp: fix runtime configmmap issue
Date: Tue, 5 Nov 2019 15:14:51 +0100 [thread overview]
Message-ID: <CAJFAV8zuWrA8sef3yZQWFVmi+itF48m_6_=-cF-Qv=uTCe_AHQ@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8y4pO_+M4GYbhiZN=WTO-1V-vktnVm1mMhGKq078VOA=g@mail.gmail.com>
Hello Li Han,
On Sat, Oct 26, 2019 at 6:07 PM David Marchand
<david.marchand@redhat.com> wrote:
> I took Anatoly patches since his work on the subject preceded your patch.
> Please, test the current master branch and see if you still have issues.
Did you have a chance to test with the -rc1 tag?
Thanks.
--
David Marchand
next prev parent reply other threads:[~2019-11-05 14:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 10:42 [dpdk-dev] [PATCH v3] lib/librte_eal/linuxapp: fix runtime config mmap issue Li Han
2019-10-23 17:46 ` Burakov, Anatoly
2019-10-24 7:37 ` David Marchand
2019-10-24 8:30 ` [dpdk-dev] [PATCH v3] lib/librte_eal/linuxapp: fix runtime configmmap issue han.li1
2019-10-24 11:13 ` [dpdk-dev] [PATCH v3] lib/librte_eal/linuxapp: fix runtime config mmap issue Burakov, Anatoly
2019-10-24 11:23 ` David Marchand
2019-10-24 12:22 ` Burakov, Anatoly
2019-10-24 12:39 ` Burakov, Anatoly
2019-10-25 11:37 ` [dpdk-dev] [PATCH v3] lib/librte_eal/linuxapp: fix runtime configmmap issue han.li1
2019-10-25 12:20 ` Burakov, Anatoly
2019-10-26 16:07 ` David Marchand
2019-11-05 14:14 ` David Marchand [this message]
2019-11-13 7:38 ` David Marchand
2019-10-24 11:13 ` [dpdk-dev] [PATCH v3] lib/librte_eal/linuxapp: fix runtime config mmap issue Burakov, Anatoly
2019-10-24 12:38 ` Burakov, Anatoly
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='CAJFAV8zuWrA8sef3yZQWFVmi+itF48m_6_=-cF-Qv=uTCe_AHQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=han.li1@zte.com.cn \
--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).