From: patchwork-bot+netdevbpf@kernel.org
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 0/3] compiler warning fixes
Date: Tue, 25 Aug 2026 04:10:11 +0000 [thread overview]
Message-ID: <178763101189.3232246.2785579847686978647.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260823235220.79790-1-stephen@networkplumber.org>
Hello:
This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Sun, 23 Aug 2026 16:51:30 -0700 you wrote:
> Three small patches that fix warnings when iproute2 is built with latest
> GCC-17 and/or Clang-21.
>
> Stephen Hemminger (3):
> json_print: fix Gcc-17 warnings
> lib: fix warning from ll_addr_a2n
> tc/f_u32: fix const strchr() warning
>
> [...]
Here is the summary with links:
- [iproute2,1/3] json_print: fix Gcc-17 warnings
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=9361f61abb6d
- [iproute2,2/3] lib: fix warning from ll_addr_a2n
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=5faf18f672c1
- [iproute2,3/3] tc/f_u32: fix const strchr() warning
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=21a61425cb9a
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-08-25 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 23:51 [PATCH iproute2 0/3] compiler warning fixes Stephen Hemminger
2026-08-23 23:51 ` [PATCH iproute2 1/3] json_print: fix Gcc-17 warnings Stephen Hemminger
2026-08-23 23:51 ` [PATCH iproute2 2/3] lib: fix warning from ll_addr_a2n Stephen Hemminger
2026-08-23 23:51 ` [PATCH iproute2 3/3] tc/f_u32: fix const strchr() warning Stephen Hemminger
2026-08-25 4:10 ` 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=178763101189.3232246.2785579847686978647.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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