From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Marchand <david.marchand@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] maintainers: claim eal common and linux
Date: Mon, 09 Feb 2015 16:26:45 +0100 [thread overview]
Message-ID: <20336259.iv3HQuiV0i@xps13> (raw)
In-Reply-To: <1423489843-4455-1-git-send-email-david.marchand@6wind.com>
2015-02-09 14:50, David Marchand:
> As discussed with Thomas, I would like to take care of the common eal and linux
> implementation.
>
> Signed-off-by: David Marchand <david.marchand@6wind.com>
[...]
> EAL API and common code
> -M: Thomas Monjalon <thomas.monjalon@6wind.com>
> +M: David Marchand <david.marchand@6wind.com>
Thank you David to assume this responsibility.
You have already done an excellent job in EAL reviews and cleanups,
especially for arch split.
> Linux EAL (with overlaps)
> +M: David Marchand <david.marchand@6wind.com>
Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Applied, thanks
prev parent reply other threads:[~2015-02-09 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 13:50 David Marchand
2015-02-09 15:26 ` 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=20336259.iv3HQuiV0i@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.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).