From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: <stable@dpdk.org>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/4] common/sfc_efx: use correct define to control debug
Date: Fri, 5 Nov 2021 21:07:17 +0000 [thread overview]
Message-ID: <69bf7753-a370-09ac-bffb-a8166be7c0c0@intel.com> (raw)
In-Reply-To: <20211105083333.1960017-2-andrew.rybchenko@oktetlabs.ru>
On 11/5/2021 8:33 AM, Andrew Rybchenko wrote:
> efsys.h belongs to common/sfc_efx and common driver debug
> toggle should be used instead of net/sfc toggle.
>
> Fixes: 5e111ed87999 ("net/sfc: introduce common driver library")
> Cc: stable@dpdk.org
>
> Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Not the set, only for this individual patch,
Applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2021-11-05 21:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 8:33 [dpdk-dev] [PATCH 0/4] net/sfc: support SN1022 SoC Andrew Rybchenko
2021-11-05 8:33 ` [dpdk-dev] [PATCH 1/4] common/sfc_efx: use correct define to control debug Andrew Rybchenko
2021-11-05 21:07 ` Ferruh Yigit [this message]
2021-11-05 8:33 ` [dpdk-dev] [PATCH 2/4] common/sfc_efx/base: support NIC DMA memory regions API Andrew Rybchenko
2021-11-05 8:33 ` [dpdk-dev] [PATCH 3/4] net/sfc: make adapter lock recursive Andrew Rybchenko
2021-11-05 8:33 ` [dpdk-dev] [PATCH 4/4] net/sfc: support regioned NIC DMA memory mapping type Andrew Rybchenko
2021-11-05 19:05 ` Ferruh Yigit
2021-11-05 20:14 ` Thomas Monjalon
2021-11-06 8:39 ` Andrew Rybchenko
2021-11-06 8:48 ` Thomas Monjalon
2021-11-17 7:05 ` [PATCH v2 0/2] net/sfc: support SN1022 SoC Andrew Rybchenko
2021-11-17 7:05 ` [PATCH v2 1/2] common/sfc_efx/base: support NIC DMA memory regions API Andrew Rybchenko
2021-11-17 7:05 ` [PATCH v2 2/2] net/sfc: support regioned NIC DMA memory mapping type Andrew Rybchenko
2021-11-17 11:44 ` [PATCH v2 0/2] net/sfc: support SN1022 SoC 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=69bf7753-a370-09ac-bffb-a8166be7c0c0@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=stable@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).