All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Aswin Karuvally <aswin@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, andrew+netdev@lunn.ch,
	netdev@vger.kernel.org, linux-s390@vger.kernel.org,
	hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
	wintera@linux.ibm.com, borntraeger@linux.ibm.com,
	svens@linux.ibm.com, horms@kernel.org
Subject: Re: [PATCH net-next] s390/ctcm: Use info level for handshake UC_RCRESET
Date: Thu, 06 Nov 2025 14:30:06 +0000	[thread overview]
Message-ID: <176243940650.230375.7618185802650828717.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251103101652.2349855-1-aswin@linux.ibm.com>

Hello:

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

On Mon,  3 Nov 2025 11:16:52 +0100 you wrote:
> CTC adapter throws CTC_EVENT_UC_RCRESET (Unit check remote reset event)
> during initial handshake, if the peer is not ready yet. This causes the
> ctcm driver to re-attempt the handshake.
> 
> As it is normal for the event to occur during initialization, use info
> instead of warn level in kernel log and NOTICE instead of ERROR level
> in s390 debug feature. Also reword the log message for clarity.
> 
> [...]

Here is the summary with links:
  - [net-next] s390/ctcm: Use info level for handshake UC_RCRESET
    https://git.kernel.org/netdev/net-next/c/0cc4b8461591

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



      reply	other threads:[~2025-11-06 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 10:16 [PATCH net-next] s390/ctcm: Use info level for handshake UC_RCRESET Aswin Karuvally
2025-11-06 14:30 ` 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=176243940650.230375.7618185802650828717.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=aswin@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=svens@linux.ibm.com \
    --cc=wintera@linux.ibm.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.