public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Maciej W. Rozycki <macro@orcam.me.uk>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] declance: Improve DMA error reporting
Date: Wed, 01 Apr 2026 02:40:09 +0000	[thread overview]
Message-ID: <177501120929.3042140.7144845991669708956.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2603291835550.60268@angie.orcam.me.uk>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun, 29 Mar 2026 19:07:18 +0100 (BST) you wrote:
> Hi,
> 
>  D'oh, this v2 fixes a silly thinko in the commit description of 2/2.
> 
>  Inspired by a recent discussion[1] I have come up with this pair of
> small improvements to DMA error reporting with declance.  Please apply.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] declance: Rate-limit DMA errors
    https://git.kernel.org/netdev/net-next/c/ee769323b1bf
  - [net-next,v2,2/2] declance: Include the offending address with DMA errors
    https://git.kernel.org/netdev/net-next/c/aae5efaeb8aa

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



      parent reply	other threads:[~2026-04-01  2:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29 18:07 [PATCH net-next v2 0/2] declance: Improve DMA error reporting Maciej W. Rozycki
2026-03-29 18:07 ` [PATCH net-next v2 1/2] declance: Rate-limit DMA errors Maciej W. Rozycki
2026-03-29 18:07 ` [PATCH net-next v2 2/2] declance: Include the offending address with " Maciej W. Rozycki
2026-04-01  2:40 ` 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=177501120929.3042140.7144845991669708956.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --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