From: Stephen Hemminger <stephen@networkplumber.org>
To: William Bland <blandwwa@gmail.com>
Cc: Changchun Ouyang <changchun.ouyang@intel.com>,
Huawei Xie <huawei.xhw@alibaba-inc.com>,
dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH v2 1/4] net: fix VLAN insert doc comment for shared-mbuf error code
Date: Wed, 26 Aug 2026 13:26:30 -0700 [thread overview]
Message-ID: <20260826132630.156eaaab@phoenix.local> (raw)
In-Reply-To: <20260826173842.1298754-1-blandwwa@gmail.com>
On Wed, 26 Aug 2026 13:38:38 -0400
William Bland <blandwwa@gmail.com> wrote:
> The implementation returns -EINVAL when the mbuf is shared or
> indirect, but the doc comment inaccurately stated -EPERM.
>
> Fixes: c974021a5949 ("ether: add soft vlan encap/decap")
> Cc: stable@dpdk.org
>
> Signed-off-by: William Bland <blandwwa@gmail.com>
> ---
Applied to net-next and I fixed the pre-existing error code formatting.
Turns out you need two '-' to get it to be processed as bullet list with negative number.
prev parent reply other threads:[~2026-08-26 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 17:38 [PATCH v2 1/4] net: fix VLAN insert doc comment for shared-mbuf error code William Bland
2026-08-26 17:38 ` [PATCH v2 2/4] net/af_packet: make Rx VLAN stripped flag handling explicit William Bland
2026-08-26 20:26 ` Stephen Hemminger
2026-08-26 17:38 ` [PATCH v2 3/4] net: add VLAN insert function with a TPID argument William Bland
2026-08-26 20:27 ` Stephen Hemminger
2026-08-26 17:38 ` [PATCH v2 4/4] net/af_packet: fix QinQ outer TPID on VLAN reinsertion William Bland
2026-08-26 20:26 ` Stephen Hemminger [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=20260826132630.156eaaab@phoenix.local \
--to=stephen@networkplumber.org \
--cc=blandwwa@gmail.com \
--cc=changchun.ouyang@intel.com \
--cc=dev@dpdk.org \
--cc=huawei.xhw@alibaba-inc.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