All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Juuso Rinta <juuso.rinta@nokia.com>
Cc: sgoutham@marvell.com, gakula@marvell.com, rkannoth@marvell.com,
	sbhatta@marvell.com, bbhushan2@marvell.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] octeontx2: use dev_err_probe() for deferred probe
Date: Thu, 03 Sep 2026 10:00:15 +0000	[thread overview]
Message-ID: <178842961514.3239309.11509161427420077146.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260901-octeontx2-dev-err-probe-v1-1-1b5e1affb994@nokia.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 01 Sep 2026 08:17:36 +0300 you wrote:
> The PF and VF drivers warn and return -EPROBE_DEFER when the AF has
> not programmed the RVUM revision or does not answer the mailbox READY
> message. That is expected until rvu_af has finished initializing, so
> the warning is repeated on every deferred retry.
> 
> Use dev_err_probe() instead of dev_warn() so the expected deferral is
> not printed at warning level. -EPROBE_DEFER is logged at debug level
> and the reason is recorded in devices_deferred.
> 
> [...]

Here is the summary with links:
  - [net-next] octeontx2: use dev_err_probe() for deferred probe
    https://git.kernel.org/netdev/net-next/c/e048669dccec

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-09-03 10:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01  5:17 [PATCH net-next] octeontx2: use dev_err_probe() for deferred probe Juuso Rinta
2026-09-01  5:25 ` Ratheesh Kannoth
2026-09-03 10:00 ` 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=178842961514.3239309.11509161427420077146.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=bbhushan2@marvell.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=juuso.rinta@nokia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.com \
    --cc=sbhatta@marvell.com \
    --cc=sgoutham@marvell.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.