mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ivan Vecera <ivecera@redhat.com>
Cc: netdev@vger.kernel.org, vadim.fedorenko@linux.dev,
	arkadiusz.kubalewski@intel.com, jiri@resnulli.us,
	milena.olech@intel.com, przemyslaw.kitszel@intel.com,
	kuba@kernel.org, davem@davemloft.net, michal.michalik@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] dpll: fix a false notification and report interrupted dumps
Date: Tue, 10 Nov 2026 22:10:06 +0000	[thread overview]
Message-ID: <179434860642.85266.14474839732460083236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261105131145.1010406-1-ivecera@redhat.com>

Hello:

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

On Thu,  5 Nov 2026 14:11:43 +0100 you wrote:
> Two small fixes for the DPLL core, both found by code review:
> 
> - Patch 1 stops sending a pin change notification when adding a reference
>   sync pair fails. Reproduced on a ZL30732A board.
> - Patch 2 sets NLM_F_DUMP_INTR on pin and device dumps that a registration
>   or unregistration interrupted. Such dumps can silently miss an object.
>   Reproduced with a test module.
> 
> [...]

Here is the summary with links:
  - [net,1/2] dpll: notify about a reference sync pair only if it was added
    https://git.kernel.org/netdev/net/c/7a3837929d04
  - [net,2/2] dpll: report dumps interrupted by topology changes
    (no matching commit)

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-11-10 22:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 13:11 Ivan Vecera
2026-11-05 13:11 ` [PATCH net 1/2] dpll: notify about a reference sync pair only if it was added Ivan Vecera
2026-11-05 22:14   ` Vadim Fedorenko
2026-11-10 15:25   ` Petr Oros
2026-11-05 13:11 ` [PATCH net 2/2] dpll: report dumps interrupted by topology changes Ivan Vecera
2026-11-10 15:25   ` Petr Oros
2026-11-10 22:02   ` Jakub Kicinski
2026-11-10 22: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=179434860642.85266.14474839732460083236.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=davem@davemloft.net \
    --cc=ivecera@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.michalik@intel.com \
    --cc=milena.olech@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=vadim.fedorenko@linux.dev \
    /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
all inboxes | Powered by JetHome®