DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: konstantin.ananyev@intel.com
Cc: dev@dpdk.org, Malvika Gupta <malvika.gupta@arm.com>,
	gavin.hu@arm.com, honnappa.nagarahalli@arm.com, nd@arm.com,
	Malvika Gupta <Malvika.Gupta@arm.com>
Subject: Re: [dpdk-dev] [PATCH v2] test/bpf: use hton instead of _builtin_bswap
Date: Tue, 06 Nov 2018 02:52:15 +0100	[thread overview]
Message-ID: <23031907.Wh9nppWSVZ@xps> (raw)
In-Reply-To: <20181102190808.16421-1-malvika.gupta@arm.com>

02/11/2018 20:08, Malvika Gupta:
> From: Malvika Gupta <Malvika.Gupta@arm.com>
> 
> Convert host machine endianness to networking endianness for
> comparison of incoming packets with BPF filter
> 
> Suggested-by: Brian Brooks <brian.brooks@arm.com>
> Signed-off-by: Malvika Gupta <malvika.gupta@arm.com>
> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
> Reviewed-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> Acked-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>

Not sure Konstantin really reviewed this version.
Please confirm it is OK.

  reply	other threads:[~2018-11-06  1:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 20:46 [dpdk-dev] [PATCH] test/bpf: use hton instead of __builtin_bswap Malvika Gupta
2018-08-28 20:58 ` Honnappa Nagarahalli
2018-09-04 13:56 ` Ananyev, Konstantin
2018-09-05 21:43   ` Malvika Gupta
2018-09-12 18:46     ` Malvika Gupta
2018-10-19 12:17       ` Ananyev, Konstantin
2018-10-25 16:59         ` Malvika Gupta
2018-10-27 22:00           ` Ananyev, Konstantin
2018-11-01 18:24             ` Malvika Gupta
2018-11-02 19:08 ` [dpdk-dev] [PATCH v2] test/bpf: use hton instead of _builtin_bswap Malvika Gupta
2018-11-06  1:52   ` Thomas Monjalon [this message]
2018-11-06 10:17   ` Ananyev, Konstantin
2018-11-13 22:33     ` Thomas Monjalon

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=23031907.Wh9nppWSVZ@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=gavin.hu@arm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=malvika.gupta@arm.com \
    --cc=nd@arm.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).