From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] maintainers: claim maintainership of ipc
Date: Thu, 25 Apr 2019 16:19:02 +0100 [thread overview]
Message-ID: <0ff9ba75-4628-32cd-c8c6-e4c5b07f132e@intel.com> (raw)
Message-ID: <20190425151902.9jydJapoXORQy-HfkgEHCdjfLu11_79pQUtT56TYyCw@z> (raw)
In-Reply-To: <e8795952-291a-5127-87c1-9a315bfbe875@intel.com>
On 25-Apr-19 4:17 PM, Burakov, Anatoly wrote:
> On 25-Apr-19 2:26 PM, Thomas Monjalon wrote:
>> 25/04/2019 15:17, Anatoly Burakov:
>>> IPC is a big part of secondary process infrastructure now,
>>> and I have been de-facto maintainer for it since 18.05.
>>> Update MAINTAINERS file to match.
>>>
>>> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
>>> ---
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -202,6 +202,7 @@ F: doc/guides/prog_guide/multi_proc_support.rst
>>> F: app/test/test_mp_secondary.c
>>> F: examples/multi_process/
>>> F: doc/guides/sample_app_ug/multi_process.rst
>>> +F: lib/librte_eal/common/eal_common_proc.c
>>
>> Isn't there more files related to IPC?
>> Please add it near other lib/ lines.
>>
>
> No, just this and the rte_eal.h maybe, which isn't exclusively IPC but
> has a lot of IPC-related stuff.
>
> OK, i'll send a v2.
>
Actually, there are no lib/* lines there.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-04-25 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 13:17 Anatoly Burakov
2019-04-25 13:17 ` Anatoly Burakov
2019-04-25 13:26 ` Thomas Monjalon
2019-04-25 13:26 ` Thomas Monjalon
2019-04-25 15:17 ` Burakov, Anatoly
2019-04-25 15:17 ` Burakov, Anatoly
2019-04-25 15:19 ` Burakov, Anatoly [this message]
2019-04-25 15:19 ` Burakov, Anatoly
2019-05-03 15:45 ` Thomas Monjalon
2019-05-03 15:45 ` Thomas Monjalon
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=0ff9ba75-4628-32cd-c8c6-e4c5b07f132e@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--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).