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=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=ham 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 59F4FC072B5 for ; Fri, 24 May 2019 05:05:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1284521850 for ; Fri, 24 May 2019 05:05:48 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=sifive.com header.i=@sifive.com header.b="YYbVYxF6" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731816AbfEXFFr (ORCPT ); Fri, 24 May 2019 01:05:47 -0400 Received: from mail-vs1-f67.google.com ([209.85.217.67]:42711 "EHLO mail-vs1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726450AbfEXFFr (ORCPT ); Fri, 24 May 2019 01:05:47 -0400 Received: by mail-vs1-f67.google.com with SMTP id z11so4962030vsq.9 for ; Thu, 23 May 2019 22:05:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tKVly6OsjAP22H8YmM5rdYdS5YdPghJ8QErKTSHa7AM=; b=YYbVYxF6Q9/uYNoqs8vrH9SJmroJSJaP37lSIzKdWSzQBcJ/xpe2IYe/QqzKtLyQQD +mgzMgT2mWRdPK2QGhjlfc3yBnWAp5Ugakm4AXKL10W+s6VPjL7KSE/mPQqdO2jAuY9R jf4ODaHOOT2EB/XZicSIGzsKK8LptVeP+GAkepgZi4qO4rN/gLOtSbDi0mtSiw5If5Vl xWec84BewQq084f38kXoEm2IzhMH45y7lMNMpOu6fWzJsvZC8dynWdPX2BRPH1exFtTS 6ObR92e+wS3VYIC0gN9Rx7wm/IRdcq5Vc0Ji0MLRNS/TOHs/bRN/0WfvlzFiBfPd18Uj 7+7A== 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=tKVly6OsjAP22H8YmM5rdYdS5YdPghJ8QErKTSHa7AM=; b=KUG9Qy5QAnO/FTdpDD8i2QmXFOsAKr3uvClnf5+jNPgwRQLIBEP9LMvC3q91XCNv/m gHnYHm+38YJudseup33AJXzfz+CQibZqTz4g78myvVy0kyeOdS9zddjKyNvoRSQx8+RW 6/EW6vZYG5YRi6sHiYbypagyoDcuss6plHuTuGMsfiawcuRmGnFuJPnklhJhMajKfufw 5pOKcPTVvROsRHsrtEGLtjQ7O5lBwPK/spQDxQotacoBPrNaZBUAcYXW7biQK3ZF6Oqs 15HeqIll+xc/Dg3FgwhKCc4GBFbV1xTg9yrGpZuFaG8sU3YixpmBNuHbVdp0ryDgxo7h MOyw== X-Gm-Message-State: APjAAAXSJNj052nVxc/7u857+ERxNqO0gMWXMFZGYfOpSQGMmGrBVE/I qkismIkk6t0XE7K0+2B683zKY4arswsllWix/xiW/w== X-Google-Smtp-Source: APXvYqzGNNHs++eX29nKjNVR+rLrBktRKrwzetThjxGfSuRn9WRNWCLdhEHXEO68Z8lWnHq60qbFVQOvuEi4IDCpLJo= X-Received: by 2002:a67:ca9a:: with SMTP id a26mr21338403vsl.92.1558674346247; Thu, 23 May 2019 22:05:46 -0700 (PDT) MIME-Version: 1.0 References: <1558515574-11155-1-git-send-email-sagar.kadam@sifive.com> <1558515574-11155-4-git-send-email-sagar.kadam@sifive.com> <20190522194529.GJ7281@lunn.ch> <20190523123435.GA15531@lunn.ch> <20190523135350.GA4985@kunai> In-Reply-To: <20190523135350.GA4985@kunai> From: Sagar Kadam Date: Fri, 24 May 2019 10:35:35 +0530 Message-ID: Subject: Re: [PATCH v7 3/3] i2c-ocores: sifive: add polling mode workaround for FU540-C000 SoC. To: Wolfram Sang Cc: Andrew Lunn , Rob Herring , Mark Rutland , peter@korsgaard.com, Palmer Dabbelt , Paul Walmsley , Linux I2C , devicetree@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org 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 Thu, May 23, 2019 at 7:23 PM Wolfram Sang wrote: > > > > Ok, Great. Do we need to write to him about this patchset? > > Nope. Hint: You can dig in the mail archives studying older patches to > see how things work. I do this as well because things may work > differently per subsystem. > Thanks Wolfram for confirming on this. I will do check in the mail archives for additional info. Regards, Sagar Kadam