From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] maintainers: claim EAL memory init
Date: Fri, 27 Apr 2018 23:56:28 +0200 [thread overview]
Message-ID: <3094413.UnKSu4bEqr@xps> (raw)
In-Reply-To: <811ec68f296b93b7b5f481163e93cfcbc88de74c.1524486584.git.anatoly.burakov@intel.com>
23/04/2018 14:29, Anatoly Burakov:
> Claim maintainership of all areas of EAL memory init, including
> OS-specific parts of it.
>
> Also, claim maintainership of fbarray, since although it's not
> related to memory allocation, it is heavily used by it and its
> primary purpose is to serve memory allocation functions, and
> thus will appear under "memory allocation" banner.
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
Applied, thanks for all the work/rework on memory management
prev parent reply other threads:[~2018-04-27 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 12:22 [dpdk-dev] [PATCH] eal: claim maintainership of " Anatoly Burakov
2018-04-23 12:29 ` [dpdk-dev] [PATCH v2] maintainers: claim " Anatoly Burakov
2018-04-27 21:56 ` Thomas Monjalon [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=3094413.UnKSu4bEqr@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@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).