[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <51dd8bf76aa056fbc966e48132cac2607d2326ca.20efc551.304a.4dd9.ad9e.59f1ab3bc329@bytedance.com>
Date: Fri, 09 Jan 2026 11:48:11 +0800
From: "Jian Zhang" <zhangjian.3032@...edance.com>
To: "Jeremy Kerr" <jk@...econstruct.com.au>
Cc: "Matt Johnston" <matt@...econstruct.com.au>,
"Andrew Lunn" <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
"Eric Dumazet" <edumazet@...gle.com>, "Jakub Kicinski" <kuba@...nel.org>,
"Paolo Abeni" <pabeni@...hat.com>, <netdev@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] net: mctp-i2c: fix duplicate reception of old data
Hi Jeremy,
> > The MCTP I2C slave callback did not handle I2C_SLAVE_READ_REQUESTED
> > events. As a result, i2c read event will trigger repeated reception
> > of old data, reset rx_pos when a read request is received.
>
> Makes sense. You're just invoking any i2c read from the peer controller
> to trigger this, is that right?
Yes, the peer just send a i2c read, like `i2cdetect -r -y 4`.
Jian.
Powered by blists - more mailing lists