netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 net-next 0/2] rxrpc: Fixes
Date: Thu, 15 Oct 2020 18:33:01 +0000	[thread overview]
Message-ID: <160278678121.17812.13011148239593102113.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <160276675194.955243.3551319337030732277.stgit@warthog.procyon.org.uk>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Thu, 15 Oct 2020 13:59:11 +0100 you wrote:
> Here are a couple of fixes that need to be applied on top of rxrpc patches
> in net-next:
> 
>  (1) Fix a bug in the connection bundle changes in the net-next tree.
> 
>  (2) Fix the loss of final ACK on socket shutdown.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] rxrpc: Fix bundle counting for exclusive connections
    https://git.kernel.org/netdev/net-next/c/f3af4ad1e08a
  - [net-next,2/2] rxrpc: Fix loss of final ack on shutdown
    https://git.kernel.org/netdev/net-next/c/ddc7834af8d5

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2020-10-15 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 12:59 [PATCH net-next 0/2] rxrpc: Fixes David Howells
2020-10-15 12:59 ` [PATCH net-next 1/2] rxrpc: Fix bundle counting for exclusive connections David Howells
2020-10-15 12:59 ` [PATCH net-next 2/2] rxrpc: Fix loss of final ack on shutdown David Howells
2020-10-15 18:22 ` [PATCH net-next 0/2] rxrpc: Fixes Jakub Kicinski
2020-10-15 18:33 ` 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=160278678121.17812.13011148239593102113.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;
as well as URLs for NNTP newsgroup(s).