DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Suanming Mou <suanmingm@nvidia.com>, <viacheslavo@nvidia.com>,
	<matan@nvidia.com>
Cc: <rasland@nvidia.com>, <dev@dpdk.org>
Subject: Re: [PATCH] net/mlx5: remove unused function
Date: Wed, 23 Feb 2022 18:45:59 +0000	[thread overview]
Message-ID: <958e374a-16d0-ac6d-3a1f-8b6541a67b7f@intel.com> (raw)
In-Reply-To: <20220215094623.22655-1-suanmingm@nvidia.com>

On 2/15/2022 9:46 AM, Suanming Mou wrote:
> The mlx5_l3t_prepare_entry() function is not used anymore.
> This commit removes the unused mlx5_l3t_prepare_entry() function.
> 

Can you please send the fixes tag, to document when this
function became unused?

I can add it in next-net.

> Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

<...>

  parent reply	other threads:[~2022-02-23 18:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  9:46 Suanming Mou
2022-02-22 14:44 ` Raslan Darawsheh
2022-02-23 18:45 ` Ferruh Yigit [this message]
2022-02-24  1:29   ` Suanming Mou

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=958e374a-16d0-ac6d-3a1f-8b6541a67b7f@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --cc=viacheslavo@nvidia.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).