Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933512AbbHLBdD (ORCPT ); Tue, 11 Aug 2015 21:33:03 -0400 Received: from mail-yk0-f171.google.com ([209.85.160.171]:33682 "EHLO mail-yk0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933327AbbHLBdA (ORCPT ); Tue, 11 Aug 2015 21:33:00 -0400 MIME-Version: 1.0 In-Reply-To: <20150811145521.GB1525@katana> References: <1438845731-17805-1-git-send-email-eddie.huang@mediatek.com> <1438845731-17805-3-git-send-email-eddie.huang@mediatek.com> <20150811145521.GB1525@katana> From: Daniel Kurtz Date: Wed, 12 Aug 2015 09:32:40 +0800 X-Google-Sender-Auth: ltOgfA1jhzmnKnno_h32wtgnAUU Message-ID: Subject: Re: [PATCH v2 2/2] i2c: mediatek: Fixup i2c ack error interrupt handling To: Wolfram Sang Cc: Eddie Huang , srv_heupstream , Matthias Brugger , Liguo Zhang , Xudong Chen , Sascha Hauer , Linux I2C , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , linux-mediatek@lists.infradead.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 991 Lines: 27 Hi Wolfram, On Tue, Aug 11, 2015 at 10:55 PM, Wolfram Sang wrote: > On Thu, Aug 06, 2015 at 03:22:11PM +0800, Eddie Huang wrote: >> When occur i2c ack error, i2c controller generate two interrupts, >> first is the ack error interrupt, then the complete interrupt. >> i2c interrupt handler should keep the two interrupt value, and only >> call complete() for the complete interrupt. >> >> Signed-off-by: Liguo Zhang >> Signed-off-by: Eddie Huang > > Applied to for-next, thanks! I don't see them in [0]. [0] https://git.kernel.org/cgit/linux/kernel/git/wsa/linux.git/log/?h=i2c/for-next Am I not looking in the right place? Or, did I not wait long enough? Thanks! -Dan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/