From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] rxrpc: Fix oops and missing config conditionals
Date: Fri, 18 Nov 2022 12:20:17 +0000 [thread overview]
Message-ID: <166877401746.25544.9755255190243368737.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <166858659236.2154965.18023032361364343888.stgit@warthog.procyon.org.uk>
Hello:
This series was applied to netdev/net-next.git (master)
by David Howells <dhowells@redhat.com>:
On Wed, 16 Nov 2022 08:16:32 +0000 you wrote:
> The patches that were pulled into net-next previously[1] had some issues
> that this patchset fixes:
>
> (1) Fix missing IPV6 config conditionals.
>
> (2) Fix an oops caused by calling udpv6_sendmsg() directly on an AF_INET
> socket.
>
> [...]
Here is the summary with links:
- [net-next,1/3] rxrpc: Fix missing IPV6 #ifdef
https://git.kernel.org/netdev/net-next/c/41cf3a9156ba
- [net-next,2/3] rxrpc: Fix oops from calling udpv6_sendmsg() on AF_INET socket
https://git.kernel.org/netdev/net-next/c/6423ac2eb31e
- [net-next,3/3] rxrpc: Fix network address validation
https://git.kernel.org/netdev/net-next/c/66f6fd278c67
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-18 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 8:16 [PATCH 0/3] rxrpc: Fix oops and missing config conditionals David Howells
2022-11-16 8:16 ` [PATCH net-next 1/3] rxrpc: Fix missing IPV6 #ifdef David Howells
2022-11-16 8:16 ` [PATCH net-next 2/3] rxrpc: Fix oops from calling udpv6_sendmsg() on AF_INET socket David Howells
2022-11-16 8:16 ` [PATCH net-next 3/3] rxrpc: Fix network address validation David Howells
2022-11-18 12:20 ` 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=166877401746.25544.9755255190243368737.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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