From: Stephen Hemminger <stephen@networkplumber.org>
To: Ariel Otilibili <otilibil@eurecom.fr>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>,
stable@dpdk.org, Vamsi Attunuru <vattunuru@marvell.com>,
Apeksha Gupta <apeksha.gupta@nxp.com>,
Sachin Saxena <sachin.saxena@nxp.com>
Subject: Re: [PATCH 1/1] net/{octeon_ep,enetfec}: remove unused value
Date: Thu, 30 Jan 2025 10:39:55 -0800 [thread overview]
Message-ID: <20250130103955.4a02e230@hermes.local> (raw)
In-Reply-To: <20241218200306.546714-2-otilibil@eurecom.fr>
On Wed, 18 Dec 2024 21:00:09 +0100
Ariel Otilibili <otilibil@eurecom.fr> wrote:
> Coverity issue: 385414, 374016
> Fixes: c836a7ba33e ("net/octeon_ep: support mailbox between VF and PF")
> Fixes: bb5b5bf1e5c ("net/enetfec: support queue configuration")
> Signed-off-by: Ariel Otilibili <otilibil@eurecom.fr>
> --
> Cc: stable@dpdk.org
> Cc: Vamsi Attunuru <vattunuru@marvell.com>
> Cc: Apeksha Gupta <apeksha.gupta@nxp.com>
> Cc: Sachin Saxena <sachin.saxena@nxp.com>
> ---
> drivers/net/enetfec/enet_ethdev.c | 1 -
> drivers/net/octeon_ep/otx_ep_mbox.c | 3 ---
> 2 files changed, 4 deletions(-)
The standard has changed (in upstream Linux checkpatch) to require longer commit id.
### [PATCH] net/{octeon_ep,enetfec}: remove unused value
WARNING:BAD_FIXES_TAG: Please use correct Fixes: style 'Fixes: <12+ chars of sha1> ("<title line>")' - ie: 'Fixes: c836a7ba33ee ("net/octeon_ep: support mailbox between VF and PF")'
#7:
Fixes: c836a7ba33e ("net/octeon_ep: support mailbox between VF and PF")
WARNING:BAD_FIXES_TAG: Please use correct Fixes: style 'Fixes: <12+ chars of sha1> ("<title line>")' - ie: 'Fixes: bb5b5bf1e5c6 ("net/enetfec: support queue configuration")'
#8:
Fixes: bb5b5bf1e5c ("net/enetfec: support queue configuration")
Fixed that and applied to next-net
next prev parent reply other threads:[~2025-01-30 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 20:00 [PATCH 0/1] " Ariel Otilibili
2024-12-18 20:00 ` [PATCH 1/1] " Ariel Otilibili
2025-01-30 18:39 ` Stephen Hemminger [this message]
2025-01-30 19:47 ` Ariel Otilibili-Anieli
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=20250130103955.4a02e230@hermes.local \
--to=stephen@networkplumber.org \
--cc=apeksha.gupta@nxp.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=otilibil@eurecom.fr \
--cc=sachin.saxena@nxp.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=vattunuru@marvell.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).