linux-kernel - Re: [PATCH v2] i2c: aspeed: Fix the dummy irq expected print

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <170972614153.1712532.8035778125665215281.b4-ty@kernel.org>
Date: Wed, 06 Mar 2024 12:55:41 +0100
From: Andi Shyti <andi.shyti@...nel.org>
To: brendan.higgins@...ux.dev, benh@...nel.crashing.org, joel@....id.au, 
 andrew@...econstruct.com.au, jae.hyun.yoo@...ux.intel.com, wsa@...nel.org, 
 Tommy Huang <tommy_huang@...eedtech.com>
Cc: linux-i2c@...r.kernel.org, openbmc@...ts.ozlabs.org, 
 linux-arm-kernel@...ts.infradead.org, linux-aspeed@...ts.ozlabs.org, 
 linux-kernel@...r.kernel.org, BMC-SW@...eedtech.com
Subject: Re: [PATCH v2] i2c: aspeed: Fix the dummy irq expected print

Hi

On Tue, 05 Mar 2024 09:19:06 +0800, Tommy Huang wrote:
> When the i2c error condition occurred and master state was not
> idle, the master irq function will goto complete state without any
> other interrupt handling. It would cause dummy irq expected print.
> Under this condition, assign the irq_status into irq_handle.
> 
> For example, when the abnormal start / stop occurred (bit 5) with
> normal stop status (bit 4) at same time. Then the normal stop status
> would not be handled and it would cause irq expected print in
> the aspeed_i2c_bus_irq.
> 
> [...]

Applied to i2c/i2c-host-fixes on

git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git

Thank you,
Andi

Patches applied
===============
[1/1] i2c: aspeed: Fix the dummy irq expected print
      commit: 94e889260a5bae7d4c06de90f1724aeb8b1175c6