From: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>,
David Marchand <david.marchand@redhat.com>
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>, dev <dev@dpdk.org>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal: fix lcore state bug
Date: Wed, 20 May 2020 14:47:32 +0200 [thread overview]
Message-ID: <63f3b99e-6ce8-5814-eb9c-97b75aa9eeaa@partner.samsung.com> (raw)
In-Reply-To: <BYAPR11MB3143FC118D514CF700463911D7B60@BYAPR11MB3143.namprd11.prod.outlook.com>
W dniu 20.05.2020 o 13:40, Van Haaren, Harry pisze:
>> -----Original Message-----
>> From: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
>> Sent: Monday, May 18, 2020 7:43 PM
>> To: David Marchand <david.marchand@redhat.com>; Van Haaren, Harry
>> <harry.van.haaren@intel.com>
>> Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>; dev <dev@dpdk.org>; dpdk
>> stable <stable@dpdk.org>
>> Subject: Re: [PATCH] eal: fix lcore state bug
>>
>>
>> W dniu 18.05.2020 o 20:39, David Marchand pisze:
>>> On Mon, May 18, 2020 at 8:25 PM Lukasz Wojciechowski
>>> <l.wojciechow@partner.samsung.com> wrote:
>>>> Hi David,
>>>>
>>>> The patch is here for quite a while and I believe it's assign to you.
>>>> Today there were some questions about it on
>>>> https://protect2.fireeye.com/url?k=a0a7498c-fd694ac1-a0a6c2c3-
>> 000babff24ad-
>> 7a5364411def2fdf&q=1&u=https%3A%2F%2Fbugs.dpdk.org%2Fshow_bug.cgi%3F
>> id%3D464
>>>> Is there anything else to be done, so it can be accepted?
>>> I want a clear ACK from a maintainer.
>>> Here Harry, since this is services specific code.
>>> The current discussion seems unfinished to me, maybe Harry can conclude?
>>>
>>> Besides, I am reluctant to take EAL changes in rc3 (out of compilation
>>> fixes or fixes for problems introduced in the current release).
>> Thanks for the answer.
>>
>> Let's wait for Harry's opinion and come back to the topic after current
>> release.
>>
>> Sorry for the rush.
> Hi Lukasz,
>
> Also reluctant to make changes in RC3, so let's fix early in the 20.08 timeframe.
> Will schedule some time to dig into the detail here and provide detailed input.
>
> Regards, -Harry
No problem, all in good time.
Thanks,
Lukasz
--
Lukasz Wojciechowski
Principal Software Engineer
Samsung R&D Institute Poland
Samsung Electronics
Office +48 22 377 88 25
l.wojciechow@partner.samsung.com
next prev parent reply other threads:[~2020-05-20 12:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200428012204eucas1p120a84e501d0d64145c21476cd2562f36@eucas1p1.samsung.com>
2020-04-28 1:21 ` Lukasz Wojciechowski
2020-04-29 3:11 ` Ruifeng Wang
2020-04-29 15:07 ` Phil Yang
2020-04-29 21:32 ` Lukasz Wojciechowski
2020-04-30 2:54 ` Phil Yang
2020-04-30 9:06 ` Lukasz Wojciechowski
2020-05-08 16:12 ` Van Haaren, Harry
2020-05-08 17:04 ` Lukasz Wojciechowski
2020-05-18 18:25 ` Lukasz Wojciechowski
2020-05-18 18:39 ` David Marchand
2020-05-18 18:43 ` Lukasz Wojciechowski
2020-05-20 11:40 ` Van Haaren, Harry
2020-05-20 12:47 ` Lukasz Wojciechowski [this message]
[not found] ` <CGME20200708133748eucas1p2dbe34d8605d8f618559daee9cbeaa73d@eucas1p2.samsung.com>
2020-07-08 13:37 ` [dpdk-dev] [PATCH v2] " Lukasz Wojciechowski
2020-07-08 14:52 ` Van Haaren, Harry
2020-07-08 17:10 ` David Marchand
2020-07-08 19:37 ` Lukasz Wojciechowski
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=63f3b99e-6ce8-5814-eb9c-97b75aa9eeaa@partner.samsung.com \
--to=l.wojciechow@partner.samsung.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=stable@dpdk.org \
/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).