From: patchwork-bot+netdevbpf@kernel.org
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: jie.luo@oss.qualcomm.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] net: ethernet: qualcomm: Unconstify function arguments passed by value
Date: Tue, 07 Jul 2026 09:50:07 +0000 [thread overview]
Message-ID: <178341780740.1462730.2151997289805409104.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260702094908.79859-3-krzysztof.kozlowski@oss.qualcomm.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 2 Jul 2026 11:49:09 +0200 you wrote:
> There is no benefit in marking "const" a pass-by-value (not a pointer)
> function argument, because it is passed as a copy on the stack. No code
> readability improvements, no additional compiler-time safety for misuse.
> Drop such redundant "const".
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: ethernet: qualcomm: Unconstify function arguments passed by value
https://git.kernel.org/netdev/net-next/c/e0421c6fd39d
- [net-next,2/2] net: ethernet: qualcomm: Constify "queue_map" in ppe_ring_queue_map_set()
https://git.kernel.org/netdev/net-next/c/cefd16657c1d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-07 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 9:49 [PATCH net-next 1/2] net: ethernet: qualcomm: Unconstify function arguments passed by value Krzysztof Kozlowski
2026-07-02 9:49 ` [PATCH net-next 2/2] net: ethernet: qualcomm: Constify "queue_map" in ppe_ring_queue_map_set() Krzysztof Kozlowski
2026-07-03 8:06 ` Jie Luo
2026-07-03 8:07 ` [PATCH net-next 1/2] net: ethernet: qualcomm: Unconstify function arguments passed by value Jie Luo
2026-07-07 9:50 ` patchwork-bot+netdevbpf [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=178341780740.1462730.2151997289805409104.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jie.luo@oss.qualcomm.com \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.