All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: ALOK TIWARI <alok.a.tiwari@oracle.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net] xirc2ps_cs: fix register access when enabling FullDuplex
Date: Sat, 30 Aug 2025 02:20:09 +0000	[thread overview]
Message-ID: <175652040950.2398246.15475699661279507232.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250827192645.658496-1-alok.a.tiwari@oracle.com>

Hello:

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

On Wed, 27 Aug 2025 12:26:43 -0700 you wrote:
> The current code incorrectly passes (XIRCREG1_ECR | FullDuplex) as
> the register address to GetByte(), instead of fetching the register
> value and OR-ing it with FullDuplex. This results in an invalid
> register access.
> 
> Fix it by reading XIRCREG1_ECR first, then or-ing with FullDuplex
> before writing it back.
> 
> [...]

Here is the summary with links:
  - [net] xirc2ps_cs: fix register access when enabling FullDuplex
    https://git.kernel.org/netdev/net/c/b79e498080b1

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



      parent reply	other threads:[~2025-08-30  2:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27 19:26 [PATCH net] xirc2ps_cs: fix register access when enabling FullDuplex Alok Tiwari
2025-08-28 17:21 ` Simon Horman
2025-08-28 18:49   ` [External] : " ALOK TIWARI
2025-08-28 21:36     ` Jacob Keller
2025-08-30  2:20 ` 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=175652040950.2398246.15475699661279507232.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alok.a.tiwari@oracle.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@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.