From: patchwork-bot+netdevbpf@kernel.org
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com,
matthieu.baerts@tessares.net, mptcp@lists.linux.dev
Subject: Re: [PATCH net-next 0/2] mptcp: More specific netlink command errors
Date: Mon, 21 Nov 2022 13:10:16 +0000 [thread overview]
Message-ID: <166903621674.4573.13888635392662727952.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221118184608.187932-1-mathew.j.martineau@linux.intel.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 18 Nov 2022 10:46:06 -0800 you wrote:
> This series makes the error reporting for the MPTCP_PM_CMD_ADD_ADDR netlink
> command more specific, since there are multiple reasons the command could
> fail.
>
> Note that patch 2 adds a GENL_SET_ERR_MSG_FMT() macro to genetlink.h,
> which is outside the MPTCP subsystem.
>
> [...]
Here is the summary with links:
- [net-next,1/2] mptcp: deduplicate error paths on endpoint creation
https://git.kernel.org/netdev/net-next/c/976d302fb616
- [net-next,2/2] mptcp: more detailed error reporting on endpoint creation
https://git.kernel.org/netdev/net-next/c/a3400e8746b6
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-11-21 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 18:46 [PATCH net-next 0/2] mptcp: More specific netlink command errors Mat Martineau
2022-11-18 18:46 ` [PATCH net-next 1/2] mptcp: deduplicate error paths on endpoint creation Mat Martineau
2022-11-18 18:46 ` [PATCH net-next 2/2] mptcp: more detailed error reporting " Mat Martineau
2022-11-21 13: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=166903621674.4573.13888635392662727952.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--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 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).