From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, sthemmin@microsoft.com, dsahern@gmail.com
Subject: Re: [patch iproute2-next 0/2] devlink: fix couple of cosmetic issues
Date: Thu, 29 Sep 2022 15:00:16 +0000 [thread overview]
Message-ID: <166446361642.22433.2425220805651992484.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220929102436.3047138-1-jiri@resnulli.us>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:
On Thu, 29 Sep 2022 12:24:34 +0200 you wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> Just cosmetics, more or less.
>
> Jiri Pirko (2):
> devlink: move use_iec into struct dl
> devlink: fix typo in variable name in ifname_map_cb()
>
> [...]
Here is the summary with links:
- [iproute2-next,1/2] devlink: move use_iec into struct dl
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=16d2732a5283
- [iproute2-next,2/2] devlink: fix typo in variable name in ifname_map_cb()
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=d8d3aadf347c
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:[~2022-09-29 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 10:24 [patch iproute2-next 0/2] devlink: fix couple of cosmetic issues Jiri Pirko
2022-09-29 10:24 ` [patch iproute2-next 1/2] devlink: move use_iec into struct dl Jiri Pirko
2022-09-29 10:24 ` [patch iproute2-next 2/2] devlink: fix typo in variable name in ifname_map_cb() Jiri Pirko
2022-09-29 15:00 ` 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=166446361642.22433.2425220805651992484.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@gmail.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.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).