From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "He, Shaopeng" <shaopeng.he@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] fm10k: support XEN domain0
Date: Wed, 01 Jul 2015 12:47:24 +0200 [thread overview]
Message-ID: <3937025.fl7qCHlTup@xps13> (raw)
In-Reply-To: <FB82FCC69332B84596FE0CEC3C1310949EBFC9@shsmsx102.ccr.corp.intel.com>
2015-06-30 03:27, He, Shaopeng:
> From: He, Shaopeng
> > From: Liu, Jijiang
> > > Acked-by: Jijiang Liu <Jijiang.liu@intel.com>
> > >
> > > I think this patch could be merged before Stephen's following patch[1] is
> > > merged, then Stephen should rework the patch[1].
> > > Thanks.
> > >
> > > [1]http://dpdk.org/ml/archives/dev/2015-March/014992.html
> >
> > Do you think we can accept this patch in current no-so-elegant way, so user
> > can
> > use XEN with fm10k from release 2.1; or better to wait for Stephen's patch?
> > Thank you in advance for your attention to this matter.
>
> This patch is necessary for fm10k to use on XEN environment with DPDK. How could
> we move forward, could you please kindly give some advice?
Applied.
It's probably the last time this ifdef is used. Next time, we'll have to introduce
a function which is common to Xen and standard case. A rework is welcome.
The Xen case could also be switched at run-time. Stephen's patch must be
reviewed for that.
prev parent reply other threads:[~2015-07-01 10:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 8:56 [PATCH] fm10k: support XEN domain0 Shaopeng He
2015-05-15 10:21 ` Thomas Monjalon
2015-05-15 23:57 ` Stephen Hemminger
2015-05-18 2:23 ` Liu, Jijiang
2015-06-02 3:27 ` He, Shaopeng
2015-06-05 3:17 ` Liu, Jijiang
2015-06-23 1:21 ` He, Shaopeng
2015-06-30 3:27 ` He, Shaopeng
2015-07-01 10:47 ` 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=3937025.fl7qCHlTup@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=shaopeng.he@intel.com \
/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.