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 X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1FA2FCA9EA0 for ; Fri, 25 Oct 2019 04:52:06 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E56CF21929 for ; Fri, 25 Oct 2019 04:52:05 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="G1L77h5L" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2392653AbfJYEwE (ORCPT ); Fri, 25 Oct 2019 00:52:04 -0400 Received: from mail-lf1-f67.google.com ([209.85.167.67]:36706 "EHLO mail-lf1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732606AbfJYEwE (ORCPT ); Fri, 25 Oct 2019 00:52:04 -0400 Received: by mail-lf1-f67.google.com with SMTP id u16so599166lfq.3 for ; Thu, 24 Oct 2019 21:52:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YmH4co9M+ZSsgCt8IZXd3+esyhYdCc0EXhkw0YqcSCs=; b=G1L77h5L6Hu8ngA1fW2Hs+AazniThA9Zqssrirkcm/tG7cam7B2ULQrQky8ApcCjQf BYDSeBr3KPlxNVkqMFhhcGM24x/rqgchiQZZ2AE9GRILdUzB+gC8f0/+PWXe+ATVR23O EVg6zZ4nQ/gWPmFKj1nG5S9NTbZuiQ0rQj7bc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YmH4co9M+ZSsgCt8IZXd3+esyhYdCc0EXhkw0YqcSCs=; b=UP8BRUgda2wCRinXn8skEHZraz8pEudEE0+gdDzzpBOeQI1lh0zBKz4Y2eJLPV7KoZ m48RCn/XSu/4lfIURtWN7I31iPfnfqDCilxvqbQkisrpIW9XGS+jcSCPXCj0ecJ8NZU1 t4puEjgGLaBsjS4GH3UYuBErkpuupKRJFc70UcFx89IIxkE9npGNlMptxGDA7mkxDuUx nGSTs/xeS1/n8hHqxYnMs0HHWEld3V59BLHSIwnt/y3IT5DhxizaRx5NSZaW4KH8pYVY rsukdQTVg9kL3l0bouRYCyelL01xTjX+0suyU01wWH2WRkGejdf9xwFquHzlBbGMyklx /4nw== X-Gm-Message-State: APjAAAXSW5x1uI0bJwMvAG4lnYjUOzdFwKvsuOVcT/yBrCGPo1v46w/W qKH3aZx3ced+mdBQyyLbAVArzmG1eMeN4c0s+OWumA== X-Google-Smtp-Source: APXvYqyzvCADhCjLC3w+Kn5bN11jVlzo8YcU37wvGQvuo5kjy90lV4V+CZGv0RYVRJMOcXh1iwgKckj0ufBBjYpHf9Q= X-Received: by 2002:ac2:4c38:: with SMTP id u24mr990839lfq.45.1571979122321; Thu, 24 Oct 2019 21:52:02 -0700 (PDT) MIME-Version: 1.0 References: <1569825869-30640-1-git-send-email-rayagonda.kokatanur@broadcom.com> <20191024185540.GF1870@kunai> In-Reply-To: <20191024185540.GF1870@kunai> From: Rayagonda Kokatanur Date: Fri, 25 Oct 2019 10:21:51 +0530 Message-ID: Subject: Re: [PATCH v2 1/1] i2c: iproc: Add i2c repeated start capability To: Wolfram Sang Cc: Ray Jui , Scott Branden , BCM Kernel Feedback , Michael Cheng , Shreesha Rajashekar , Lori Hikichi , linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Linux Kernel Mailing List , Icarus Chau , Ray Jui , Shivaraj Shetty Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 25, 2019 at 12:25 AM Wolfram Sang wrote: > > On Mon, Sep 30, 2019 at 12:14:29PM +0530, Rayagonda Kokatanur wrote: > > From: Lori Hikichi > > > > Enable handling of i2c repeated start. The current code > > handles a multi msg i2c transfer as separate i2c bus > > transactions. This change will now handle this case > > using the i2c repeated start protocol. The number of msgs > > in a transfer is limited to two, and must be a write > > followed by a read. > > > > Signed-off-by: Lori Hikichi > > Signed-off-by: Rayagonda Kokatanur > > Signed-off-by: Icarus Chau > > Signed-off-by: Ray Jui > > Signed-off-by: Shivaraj Shetty > > Patch looks good but doesn't apply for me on top of v5.4-rc4? What was > your base? > > Also, I will apply it to for-next (v5.5). If you want it for v5.4, then > please add a Fixes tag. > thank you, please apply it to for-next (v5.5). Do I need to resend patch again for you to apply it to v5.5 ?