From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>, dev@dpdk.org
Cc: vishal@chelsio.com, nirranjan@chelsio.com, indranil@chelsio.com
Subject: Re: [dpdk-dev] [PATCH] net/cxgbe: remove unused code in Rx path
Date: Thu, 21 Mar 2019 19:45:07 +0000 [thread overview]
Message-ID: <5ed80b9f-394c-8068-e17c-f4fa4439ff99@intel.com> (raw)
Message-ID: <20190321194507.lpdFJnWY-0uDcWAjK06SS8lDHrfsemdOkSb32fY9CU8@z> (raw)
In-Reply-To: <1553082556-20489-1-git-send-email-rahul.lakkireddy@chelsio.com>
On 3/20/2019 11:49 AM, Rahul Lakkireddy wrote:
> From: Vishal Kulkarni <vishal@chelsio.com>
>
> All Rx packet handling is done in process_responses() and hence
> t4_ethrx_handler() never gets called. So, remove it.
>
> Signed-off-by: Vishal Kulkarni <vishal@chelsio.com>
> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-03-21 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 11:49 Rahul Lakkireddy
2019-03-20 11:49 ` Rahul Lakkireddy
2019-03-21 19:45 ` Ferruh Yigit [this message]
2019-03-21 19:45 ` 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=5ed80b9f-394c-8068-e17c-f4fa4439ff99@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=indranil@chelsio.com \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=vishal@chelsio.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).