From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH 6/6] fm10k: use rte_eth_dma_zone_reserve
Date: Wed, 21 Oct 2015 16:37:21 +0200 [thread overview]
Message-ID: <3089798.UWYHkBV93j@xps13> (raw)
In-Reply-To: <CALwxeUtE5KBMvG+-UF15xxmX5McuJqoGjUnDJS=roDwmE3V1aw@mail.gmail.com>
2015-10-04 20:44, David Marchand:
> On Tue, Sep 29, 2015 at 2:44 AM, Stephen Hemminger <
> > --- a/drivers/net/fm10k/fm10k_ethdev.c
> > +++ b/drivers/net/fm10k/fm10k_ethdev.c
> > -#ifdef RTE_LIBRTE_XEN_DOM0
> > q->hw_ring_phys_addr = rte_mem_phy2mch(mz->memseg_id,
> > mz->phys_addr);
> > -#else
> > q->hw_ring_phys_addr = mz->phys_addr;
> > -#endif
>
> "else" part has been forgotten.
I could fix it before applying but it would be saner to have a v2.
patchwork status: change requested
next prev parent reply other threads:[~2015-10-21 14:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 0:44 [PATCH 0/6] Xen DOM0 runtime support Stephen Hemminger
2015-09-29 0:44 ` [PATCH 1/6] xen: allow determining DOM0 at runtime Stephen Hemminger
2015-10-21 14:41 ` Thomas Monjalon
2015-09-29 0:44 ` [PATCH 2/6] ethdev: add common function for reserving DMA regions Stephen Hemminger
2015-09-29 0:44 ` [PATCH 3/6] e1000: use rte_eth_dma_zone_reserve Stephen Hemminger
2015-09-29 0:44 ` [PATCH 4/6] ixgbe: " Stephen Hemminger
2015-09-29 0:44 ` [PATCH 5/6] i40e: " Stephen Hemminger
2015-09-29 0:44 ` [PATCH 6/6] fm10k: " Stephen Hemminger
2015-10-04 18:44 ` David Marchand
2015-10-21 14:37 ` Thomas Monjalon [this message]
2015-09-29 20:11 ` [PATCH 0/6] Xen DOM0 runtime support Liu, Jijiang
2015-09-30 8:14 ` David Marchand
2015-09-30 17:30 ` Stephen Hemminger
2015-10-21 14:40 ` Thomas Monjalon
2015-10-23 6:28 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2015-10-23 6:34 [PATCH v2 " Stephen Hemminger
2015-10-23 6:34 ` [PATCH 6/6] fm10k: use rte_eth_dma_zone_reserve Stephen Hemminger
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=3089798.UWYHkBV93j@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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.