public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: jk@codeconstruct.com.au, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, wsa@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, andrew@codeconstruct.com.au
Subject: Re: [PATCH net-next] mctp i2c: initialise event handler read bytes
Date: Mon, 19 Jan 2026 14:19:37 +0000	[thread overview]
Message-ID: <176883237711.1426077.5900427091138525650.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260113-mctp-read-fix-v1-1-70c4b59c741c@codeconstruct.com.au>

Hello:

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

On Tue, 13 Jan 2026 17:01:16 +0800 you wrote:
> Set a 0xff value for i2c reads of an mctp-i2c device. Otherwise reads
> will return "val" from the i2c bus driver. For i2c-aspeed and
> i2c-npcm7xx that is a stack uninitialised u8.
> 
> Tested with "i2ctransfer -y 1 r10@0x34" where 0x34 is a mctp-i2c
> instance, now it returns all 0xff.
> 
> [...]

Here is the summary with links:
  - [net-next] mctp i2c: initialise event handler read bytes
    https://git.kernel.org/netdev/net-next/c/2a14e91b6d76

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



      reply	other threads:[~2026-01-19 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13  9:01 [PATCH net-next] mctp i2c: initialise event handler read bytes Matt Johnston
2026-01-19 14:19 ` 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=176883237711.1426077.5900427091138525650.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@codeconstruct.com.au \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jk@codeconstruct.com.au \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeconstruct.com.au \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wsa@kernel.org \
    /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