From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: xuelin.shi@freescale.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ixgbe: fix data access on big endian cpu
Date: Mon, 23 Mar 2015 15:01:53 +0100 [thread overview]
Message-ID: <3986979.AOFPnzYeq1@xps13> (raw)
In-Reply-To: <1425371224-15631-1-git-send-email-xuelin.shi@freescale.com>
2015-03-03 16:27, xuelin.shi@freescale.com:
> From: Xuelin Shi <xuelin.shi@freescale.com>
>
> enforce rules for cpu and ixgbe exchanging data.
> 1. cpu use data owned by ixgbe must use rte_le_to_cpu_xx(...)
> 2. cpu fill data to ixgbe must use rte_cpu_to_le_xx(...)
>
> Signed-off-by: Xuelin Shi <xuelin.shi@freescale.com>
Please Xuelin, could you rebase on HEAD and fix these checkpatch errors?
ERROR:SPACING: space prohibited after that '!' (ctx:BxW)
ERROR:CODE_INDENT: code indent should use tabs where possible
+^I^I ^I ^I IXGBE_RXDADV_STAT_DD)) {$
Thanks
next prev parent reply other threads:[~2015-03-23 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 8:27 xuelin.shi
2015-03-23 14:01 ` Thomas Monjalon [this message]
2015-03-24 7:29 ` Xuelin Shi
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=3986979.AOFPnzYeq1@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=xuelin.shi@freescale.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 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).