From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Cc: Randy Schacher <stuart.schacher@broadcom.com>,
Peter Spreadborough <peter.spreadborough@broadcom.com>,
Farah Smith <farah.smith@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: remove EEM system memory support
Date: Wed, 29 Jul 2020 17:24:56 +0100 [thread overview]
Message-ID: <c2a7eff9-7b35-eaef-f5c0-07e9fc45d3af@intel.com> (raw)
In-Reply-To: <20200729004256.46924-1-ajit.khaparde@broadcom.com>
On 7/29/2020 1:42 AM, Ajit Khaparde wrote:
> From: Randy Schacher <stuart.schacher@broadcom.com>
>
> Remove the memory management scheme for Extended Exact Match
> using system memory. Using host memory scheme instead which
> was the default anyway.
>
> Fixes: b2da02480cb7 ("net/bnxt: support EEM system memory")
>
> Signed-off-by: Randy Schacher <stuart.schacher@broadcom.com>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Reviewed-by: Peter Spreadborough <peter.spreadborough@broadcom.com>
> Reviewed-by: Farah Smith <farah.smith@broadcom.com>
<...>
> @@ -29,7 +29,6 @@ sources = files('bnxt_cpr.c',
> 'tf_core/rand.c',
> 'tf_core/stack.c',
> 'tf_core/tf_em_common.c',
> - 'tf_core/tf_em_host.c',
> 'tf_core/tf_em_internal.c',
> 'tf_core/tf_rm.c',
> 'tf_core/tf_tbl.c',
I was wondering why 'tf_em_host.c' removed from meson, while 'tf_em_system.c'
file is removed and how this is working,
but it seems 'tf_em_host.c' was duplicate in meson and you are fixing it J
Since duplication is created in this release, no need to backport it, and it is
OK have it part of this patch.
next prev parent reply other threads:[~2020-07-29 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 0:42 Ajit Khaparde
2020-07-29 14:01 ` Ajit Khaparde
2020-07-29 16:24 ` Ferruh Yigit [this message]
2020-07-29 21:24 ` Ajit Khaparde
2020-07-29 21:57 ` Ferruh Yigit
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=c2a7eff9-7b35-eaef-f5c0-07e9fc45d3af@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=farah.smith@broadcom.com \
--cc=peter.spreadborough@broadcom.com \
--cc=stuart.schacher@broadcom.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).