From: Ferruh Yigit <ferruh.yigit@intel.com>
To: asomalap@amd.com, dev@dpdk.org
Cc: Ravi1.Kumar@amd.com
Subject: Re: [dpdk-dev] [PATCH v1 1/3] net/axgbe: support for rxq and txq info API
Date: Fri, 28 Feb 2020 12:23:05 +0000 [thread overview]
Message-ID: <7324cec2-9a1e-2e78-d378-16f58cd6f7a2@intel.com> (raw)
In-Reply-To: <20200228104440.1882-1-asomalap@amd.com>
On 2/28/2020 10:44 AM, asomalap@amd.com wrote:
> From: Amaranath Somalapuram <asomalap@amd.com>
>
> Adding API for axgbe_rxq_info_get, axgbe_txq_info_get
>
> Signed-off-by: Amaranath Somalapuram <asomalap@amd.com>
Hi Amaranath,
I guess you are sending patches one by one, which each end up being a new
thread, makes harder for the maintainer to follow them.
Can you please double check the "Contributing Code to DPDK":
https://doc.dpdk.org/guides/contributing/patches.html
''Shallow threading (--thread --no-chain-reply-to) is preferred for a patch
series.''
next prev parent reply other threads:[~2020-02-28 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 10:44 asomalap
2020-02-28 12:23 ` Ferruh Yigit [this message]
2020-03-02 8:16 asomalap
2020-03-14 18:16 ` Kumar, Ravi1
2020-03-16 13:32 ` 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=7324cec2-9a1e-2e78-d378-16f58cd6f7a2@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Ravi1.Kumar@amd.com \
--cc=asomalap@amd.com \
--cc=dev@dpdk.org \
/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).