DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Radu Nicolau <radu.nicolau@intel.com>, dev <dev@dpdk.org>,
	Declan Doherty <declan.doherty@intel.com>,
	"Hemant Agrawal (OSS)" <hemant.agrawal@oss.nxp.com>,
	Anoob Joseph <anoobj@marvell.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] Re: [dpdk-stable] [PATCH v2] examples/ipsec-secgw: fix potential build error
Date: Wed, 3 Nov 2021 13:55:25 +0000	[thread overview]
Message-ID: <CO6PR18MB448444157AA92D4880E6754BD88C9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8y+KJg9GkEQ_xg5j43RFfRvjpR+v9WR7LXR3vrQa4knXw@mail.gmail.com>

> > Yes this series initiated the issue, applying both the patch and the series
> now
> > On next-crypto
> 
> It means a patch of this series broke compilation, and this fix here
> should be squashed in it.
Actually no, this is definitely an issue introduced earlier and should be part of stable.
This got highlighted here as STATS_INTERVAL ifdef was removed in this series.
The compilation is broken when STATS_INTEVAL is defined in the app.

  reply	other threads:[~2021-11-03 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 10:51 [dpdk-dev] [PATCH] examples/ipsec-secgw: fix " Radu Nicolau
2021-11-03 11:56 ` [dpdk-dev] [PATCH v2] examples/ipsec-secgw: fix potential " Radu Nicolau
2021-11-03 13:08   ` Thomas Monjalon
2021-11-03 13:36     ` [dpdk-dev] [EXT] " Akhil Goyal
2021-11-03 13:42     ` [dpdk-dev] [dpdk-stable] " David Marchand
2021-11-03 13:45       ` [dpdk-dev] [EXT] " Akhil Goyal
2021-11-03 13:50         ` David Marchand
2021-11-03 13:55           ` Akhil Goyal [this message]
2021-11-03 11:58 ` [dpdk-dev] [PATCH] examples/ipsec-secgw: fix " 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=CO6PR18MB448444157AA92D4880E6754BD88C9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@oss.nxp.com \
    --cc=radu.nicolau@intel.com \
    --cc=stable@dpdk.org \
    --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).