From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
dev@dpdk.org, Haiyue Wang <haiyue.wang@intel.com>,
Bing Zhao <bingz@nvidia.com>
Subject: Re: [dpdk-dev] [RFC] net: make eCPRI header host network order
Date: Wed, 14 Jun 2023 14:57:37 -0700 [thread overview]
Message-ID: <20230614145737.753174d3@hermes.local> (raw)
In-Reply-To: <20201127190920.3312280-1-ferruh.yigit@intel.com>
On Fri, 27 Nov 2020 19:09:20 +0000
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> Other protocol structs are in the host byte order, having eCPRI in
> network byte order is insistent and error prone.
>
> Making eCPRI protocol header host byte order.
>
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
The discussion around this never concluded and there was no followon patch.
Marking it as "Changes Requested".
The most common thing for the existing headers is to declare them to be
in network byte order.
prev parent reply other threads:[~2023-06-14 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 19:09 Ferruh Yigit
2020-11-28 3:18 ` Bing Zhao
2020-11-28 3:55 ` Wang, Haiyue
2020-11-28 5:31 ` Wang, Haiyue
2020-11-28 9:07 ` Bing Zhao
2020-11-30 1:15 ` Wang, Haiyue
2023-06-14 21:57 ` Stephen Hemminger [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=20230614145737.753174d3@hermes.local \
--to=stephen@networkplumber.org \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=haiyue.wang@intel.com \
--cc=olivier.matz@6wind.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).