From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9E7B2C7EE25 for ; Fri, 9 Jun 2023 21:26:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=782EhQLcaUbv73URWsqLZCiPrSZaSgbBYQ5SCYeb7Xk=; b=qDsoPgXAc6hLE/ O2hSkRa+tJNTRLvUuMbcNXKjXQw1s33mWgeWWX352ON7gHVfjSJ3qhYGI8hrDhQ/EPAkF9gBhMpH4 lvQpRrBIN1g1TGXZRUhckIYIyKMGmoB5RJH9g+Ng/Cz8FfxP0BlS4PS84t4Gr+LXo7vW2JfqdAxZH TOxySHVVQAeI4kBRhrOzr4cW8AoO5MNv+Nb4fNO7NLSEL6J7BpjRPooYLGYwnU8KqNlA+uaoZBjrY FiMKu5cy2HH4RCj4cBzvAZMAQ+70EAJabnPjfRg0zxqsLeNjur3CmOInq7C3t62v4tnz+eDAdbGPp 8LVceRTAYcPEiU2RoESA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1q7jcQ-00EIyR-0W; Fri, 09 Jun 2023 21:26:02 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1q7jcN-00EIxG-2V for linux-arm-kernel@lists.infradead.org; Fri, 09 Jun 2023 21:26:00 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id BD1DD65C48; Fri, 9 Jun 2023 21:25:56 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 84FE8C433D2; Fri, 9 Jun 2023 21:25:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1686345956; bh=JVAjdjvrTxxiymc4a2YVsvJs2eE8Ly4rWtiHbk2Ggbs=; h=Date:From:To:Subject:References:In-Reply-To:From; b=JVkgPVEE2//Lx9LkbNdhDbCvFNV086ZinRn5yn5KPywgGF/ue0rL3AnPvhAZQ+Lks ocEkioYIj6O9NTfcekF3emWNLy/YQgbSIDlZnqRdWHMmXG3qRrHEO32/YN5ifv1WqH tjIHgapck7gidndmenjbtrMEPw+GfZFNb0ZhPowFPdgU47Wu/Qb+nvATLxh30TlZFx WeOoz3Rds9dR5o3eQO7154en6+XndyR/u1OVlBjckH//nV5PscR2ABkRHsLV7cuNBd 09xqbIxZXV7z2hSieqFgNO1ue+XJxng8nNirMGL8DOyT05lGLGtForb77hjGau+poe ncj1XtsL10FDg== Date: Fri, 9 Jun 2023 23:25:52 +0200 From: Andi Shyti To: "wsa@kernel.org" , Robert Hancock , "michal.simek@amd.com" , "shubhraj@xilinx.com" , "marex@denx.de" , "linux-arm-kernel@lists.infradead.org" , "linux-i2c@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] i2c: xiic: Don't try to handle more interrupt events after error Message-ID: <20230609212552.5o6aopv7iicej3kn@intel.intel> References: <20230606182558.1301413-1-robert.hancock@calian.com> <20230606192453.zjzz4kt76kus5hr5@intel.intel> <20230606212053.bwpoxyost4fkpati@intel.intel> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230609_142559_882657_50254330 X-CRM114-Status: GOOD ( 16.83 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Wolfram, On Fri, Jun 09, 2023 at 05:32:42PM +0200, wsa@kernel.org wrote: > > > I think the patch is correct and I will ack it: > > > > Acked-by: Andi Shyti > > > > I think, though, that this needs a proper fix and testing, in > > order to cover all the possible combinations. The scenario you > > highlighted is indeed one, but not only, potential situation that > > could arise. > > > > Can I just ask you to write a bit more in the comment to > > highlight the possible failure? > > I tend to apply it to for-current because it improves the situation. > Further improvements could be made incrementally? D'accord everyone? > OK with that! Thanks, Andi _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel