From: "John Daley (johndale)" <johndale@cisco.com>
To: "stable@dpdk.org" <stable@dpdk.org>,
"christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>
Cc: "Hyong Youb Kim (hyonkim)" <hyonkim@cisco.com>
Subject: [dpdk-stable] [PATCH 19.11] net/enic: fix flow initialization error handling
Date: Mon, 24 May 2021 18:55:26 +0000 [thread overview]
Message-ID: <BYAPR11MB25354A59DDD6ED29FA6794C5CF269@BYAPR11MB2535.namprd11.prod.outlook.com> (raw)
[ upstream commit 5aa67931ec ]
No 19.11 backport required.
Explanation:
The wrong 'Fixes' line was used in the upstream commit log for 5aa67931ec. The correct fixline is:
Fixes: bb66d562aefc ("net/enic: share flow actions with same signature")
bb66d562aefc was committed in 20.11 so there is no backport required for 19.11.
-john
reply other threads:[~2021-05-24 18:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BYAPR11MB25354A59DDD6ED29FA6794C5CF269@BYAPR11MB2535.namprd11.prod.outlook.com \
--to=johndale@cisco.com \
--cc=christian.ehrhardt@canonical.com \
--cc=hyonkim@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).