From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Jijiang Liu <jijiang.liu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] maintainer: claim review for Xen Dom0 support
Date: Thu, 05 Feb 2015 09:25:23 +0100 [thread overview]
Message-ID: <24967719.U7Dc9FlWMt@xps13> (raw)
In-Reply-To: <1423103460-4161-1-git-send-email-jijiang.liu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Hi Jijiang,
2015-02-05 10:31, Jijiang Liu:
> I will be a volunteer of reviewing the following files:
> lib/librte_eal/linuxapp/xen_dom0/*
> lib/librte_eal/linuxapp/eal/eal_xen_memory.c
> lib/librte_eal/linuxapp/eal/include/exec-env/rte_dom0_common.h
Actually, the section that you are subscribing is wider:
F: lib/librte_eal/linuxapp/xen_dom0/
F: lib/librte_eal/linuxapp/eal/*xen*
F: lib/librte_eal/linuxapp/eal/include/exec-env/rte_dom0_common.h
F: lib/librte_mempool/rte_dom0_mempool.c
F: lib/librte_pmd_xenvirt/
F: doc/guides/xen/
F: app/test-pmd/mempool_*
F: examples/vhost_xen/
> Linux Xen
> +M: Jijiang Liu <jijiang.liu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Was your intention to be responsible of the whole Xen area or
only of EAL for Xen?
--
Thomas
next prev parent reply other threads:[~2015-02-05 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 2:31 [PATCH] maintainer: claim review for Xen Dom0 support Jijiang Liu
[not found] ` <1423103460-4161-1-git-send-email-jijiang.liu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-02-05 8:25 ` Thomas Monjalon [this message]
2015-02-05 8:34 ` Liu, Jijiang
[not found] ` <1ED644BD7E0A5F4091CF203DAFB8E4CC01DCF89A-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-03-10 16:15 ` Thomas Monjalon
2015-02-09 0:41 ` Zhang, Helin
-- strict thread matches above, loose matches on Subject: below --
2015-02-05 2:24 Jijiang Liu
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=24967719.U7Dc9FlWMt@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=jijiang.liu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.