From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Hyong Youb Kim <hyonkim@cisco.com>
Cc: dev@dpdk.org, stable@dpdk.org, Hanoch Haim <hhaim@cisco.com>,
John Daley <johndale@cisco.com>
Subject: Re: [dpdk-stable] [PATCH] net/enic: fix a typo in debug message
Date: Fri, 5 Feb 2021 10:55:04 +0000 [thread overview]
Message-ID: <12492607-fefe-eaff-13a1-f4dba79244de@intel.com> (raw)
In-Reply-To: <20210205013503.14601-1-hyonkim@cisco.com>
On 2/5/2021 1:35 AM, Hyong Youb Kim wrote:
> A debug message for filter API is using a wrong flag. Use the correct
> one.
>
> Fixes: 936a9b9975e7 ("net/enic: flow API debug")
> Cc: stable@dpdk.org
>
> Reported-by: Hanoch Haim <hhaim@cisco.com>
> Signed-off-by: Hyong Youb Kim <hyonkim@cisco.com>
> Reviewed-by: John Daley <johndale@cisco.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-02-05 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 1:35 Hyong Youb Kim
2021-02-05 10:55 ` Ferruh Yigit [this message]
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=12492607-fefe-eaff-13a1-f4dba79244de@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hhaim@cisco.com \
--cc=hyonkim@cisco.com \
--cc=johndale@cisco.com \
--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).