DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gavin Hu <Gavin.Hu@arm.com>
To: "jerinj@marvell.com" <jerinj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"david.marchand@6wind.com" <david.marchand@6wind.com>,
	"jerinj@marvell.com" <jerinj@marvell.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/3] eal: introduce structure marker typedefs
Date: Fri, 20 Dec 2019 04:21:10 +0000	[thread overview]
Message-ID: <VI1PR08MB53763B97CE8197AE67ACA7FB8F2D0@VI1PR08MB5376.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20191219112507.3142025-1-jerinj@marvell.com>

Series-reviewed-by: Gavin Hu <gavin.hu@arm.com>

  parent reply	other threads:[~2019-12-20  4:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-08 11:34 [dpdk-dev] [PATCH " jerinj
2019-12-08 11:34 ` [dpdk-dev] [PATCH 2/3] drivers: use structure marker typedef in eal jerinj
2019-12-08 11:34 ` [dpdk-dev] [PATCH 3/3] mbuf: " jerinj
2019-12-10 22:46 ` [dpdk-dev] [PATCH 1/3] eal: introduce structure marker typedefs Thomas Monjalon
2019-12-19 10:34   ` Jerin Jacob
2019-12-19 11:25 ` [dpdk-dev] [PATCH v2 " jerinj
2019-12-19 11:25   ` [dpdk-dev] [PATCH v2 2/3] drivers: use structure marker typedef in eal jerinj
2019-12-19 11:25   ` [dpdk-dev] [PATCH v2 3/3] mbuf: " jerinj
2019-12-26 16:24     ` Olivier Matz
2020-01-20 21:55       ` Thomas Monjalon
2019-12-20  4:21   ` Gavin Hu [this message]
2019-12-26  8:15   ` [dpdk-dev] [PATCH v2 1/3] eal: introduce structure marker typedefs Matan Azrad
2020-01-02  6:27     ` Jerin Jacob
2020-01-02  9:48       ` Matan Azrad
2020-01-16 13:09         ` Jerin Jacob
2020-01-20 20:11   ` 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=VI1PR08MB53763B97CE8197AE67ACA7FB8F2D0@VI1PR08MB5376.eurprd08.prod.outlook.com \
    --to=gavin.hu@arm.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=nd@arm.com \
    --cc=thomas@monjalon.net \
    /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).