All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: 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 v3 0/2] netconsole: Populate dynamic entry even if netpoll fails
Date: Mon, 26 Aug 2024 16:40:31 +0000	[thread overview]
Message-ID: <172469043158.64426.9370838137438660997.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240822111051.179850-1-leitao@debian.org>

Hello:

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

On Thu, 22 Aug 2024 04:10:46 -0700 you wrote:
> The current implementation of netconsole removes the entry and fails
> entirely if netpoll fails to initialize. This approach is suboptimal, as
> it prevents reconfiguration or re-enabling of the target through
> configfs.
> 
> While this issue might seem minor if it were rare, it actually occurs
> frequently when the network module is configured as a loadable module.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/2] netpoll: Ensure clean state on setup failures
    https://git.kernel.org/netdev/net-next/c/ae5a0456e0b4
  - [net-next,v3,2/2] net: netconsole: Populate dynamic entry even if netpoll fails
    https://git.kernel.org/netdev/net-next/c/908ee298c8fb

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



      parent reply	other threads:[~2024-08-26 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 11:10 [PATCH net-next v3 0/2] netconsole: Populate dynamic entry even if netpoll fails Breno Leitao
2024-08-22 11:10 ` [PATCH net-next v3 1/2] netpoll: Ensure clean state on setup failures Breno Leitao
2024-08-22 11:10 ` [PATCH net-next v3 2/2] net: netconsole: Populate dynamic entry even if netpoll fails Breno Leitao
2024-08-26 16: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=172469043158.64426.9370838137438660997.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.