From: patchwork-bot+netdevbpf@kernel.org
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: netdev@vger.kernel.org, dsahern@kernel.org,
stephen@networkplumber.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH 1/2 iproute2-next] man: iplink: fix indentation level after inet parameter
Date: Sun, 07 Jun 2026 13:50:07 +0000 [thread overview]
Message-ID: <178084020790.216406.14685803948534975500.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260607065715.4573-1-fmancera@suse.de>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Sun, 7 Jun 2026 08:57:14 +0200 you wrote:
> The indentation for inet block opens with +8 but closes with -10. Fix
> the imbalance.
>
> Fixes: fdb064bf64e5 ("iplink: add support for setting IPv4 devconf parameters")
> Signed-off-by: Fernando Fernandez Mancera <fmancera@suse.de>
> ---
> man/man8/ip-link.8.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- [1/2,iproute2-next] man: iplink: fix indentation level after inet parameter
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=6592993853c0
- [2/2,iproute2-next] iplink: set NLA_F_NESTED for IPv4 devconf attributes
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=7340b539841d
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-06-07 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 6:57 [PATCH 1/2 iproute2-next] man: iplink: fix indentation level after inet parameter Fernando Fernandez Mancera
2026-06-07 6:57 ` [PATCH 2/2 iproute2-next] iplink: set NLA_F_NESTED for IPv4 devconf attributes Fernando Fernandez Mancera
2026-06-07 13: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=178084020790.216406.14685803948534975500.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=fmancera@suse.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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