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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DA5DCC77B6E for ; Wed, 12 Apr 2023 04:47:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229516AbjDLErG (ORCPT ); Wed, 12 Apr 2023 00:47:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58192 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229492AbjDLErF (ORCPT ); Wed, 12 Apr 2023 00:47:05 -0400 Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E3A362D57 for ; Tue, 11 Apr 2023 21:46:56 -0700 (PDT) Received: by mail-pj1-x1036.google.com with SMTP id o2-20020a17090a0a0200b00246da660bd2so3287895pjo.0 for ; Tue, 11 Apr 2023 21:46:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tweaklogic.com; s=google; t=1681274816; x=1683866816; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=+bx1peOWUY+EguIhN3+HEV80l+NpcfNfRNogKL9pYa8=; b=TYD6k5TkH0f+f2VcgwjIMuLUw5PF7L9qlFK7nKXfGEzzYqg5yocLOj1NQcTK3AlAX8 7L49b8EJyccPPe9AEmNfHPbpp9gwhlxoNTDCh0SE1hZc6MyxITgRVf7vXAHMExP+UADL dlSuONYrS5XVbWrjQ2wBV/vTEO137v89cT9dkfhh4QNwnjBK2IgJHRgEo+sMqHdnQIXb J01mLe7aZYR537STAD/H0nm6pewLefxODOua1AMHGwSXynhqlckI5SFYTlRwMFWzpF+s DjYo6pyAbx8fB4OIo6s1D7zEEreKB/Urtle6rqgWkKeAbOMUehI2F1eh3X8b6ZrwliIr s5ug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681274816; x=1683866816; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=+bx1peOWUY+EguIhN3+HEV80l+NpcfNfRNogKL9pYa8=; b=B02WeNRkILrsktdhVx8QDwFQJoc5ctLfqaUxSifkzN6d7WmaFN1QkxweQIQmJBJeGx elkP/D66DOHE+NxweDbAli2N/bMGEhYnjfJg0VIbpgn6oZqYP75aHdHDFuS6O6ah4t9b Y0Zra8ZtvOejYSvXeLB3gElZWaUz0UezaE6ZfHIs26DfOux6l78zlkf2ZirXL7+ZaVJE pfbvGiIwr51MbfvmTBjaZePlrH/1hFV00+gp05SP5iM+lA5uQw/699NONEzm9s3R3SwY EsSWSL9d6JhljSihWml++REx+Nw89OUvFow7OGAOWXTgBBCaiJ+29lEWvkHl2hvtZLVB KZew== X-Gm-Message-State: AAQBX9dtKJ+BrHQefMK11DJQvhre0h+D2ZMZVn/jDiJv6x9qZ7UJO8Mu BOcyeAywyvWTjc0CcGPqoBzjW0erTrZ+7WmlT5dX6g== X-Google-Smtp-Source: AKy350bg2rc3G/bZAa2f5cAlYhqK3olpjYj+ekBeQ1nXB59cT5PADukrzvEam2VsqAsPQONrpjRcZw== X-Received: by 2002:a17:903:2943:b0:1a4:f156:a1e3 with SMTP id li3-20020a170903294300b001a4f156a1e3mr12911958plb.58.1681274816319; Tue, 11 Apr 2023 21:46:56 -0700 (PDT) Received: from [10.240.2.163] ([124.148.245.238]) by smtp.gmail.com with ESMTPSA id f2-20020a170902860200b001a258041049sm5509039plo.32.2023.04.11.21.46.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 11 Apr 2023 21:46:55 -0700 (PDT) Message-ID: Date: Wed, 12 Apr 2023 12:46:49 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: [RFC PATCH 0/2] Support for Avago APDS9306 Ambient Light Sensor Content-Language: en-US To: Jonathan Cameron Cc: Jonathan Cameron , Lars-Peter Clausen , Rob Herring , Krzysztof Kozlowski , linux-iio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Andy Shevchenko , Shreeya Patel , Paul Gazzillo , Zhigang Shi , Dmitry Osipenko References: <20230411011203.5013-1-subhajit.ghosh@tweaklogic.com> <20230411144031.000077c7@Huawei.com> From: Subhajit Ghosh In-Reply-To: <20230411144031.000077c7@Huawei.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org Hi Jonathan, Thank you for getting back. > Hi Subhajit, > > No need to sign off a cover letter. The content isn't captured in the > git tree anyway. > > For an RFC, I'd expect to see a clear statement in the cover letter of > why it is an RFC rather than a formal patch submission. What specifically > are you looking for comments on? > > Point us in the right direction and we might answer the questions quicker. > > Thanks, > > Jonathan Thank you for clearing it up. Next version of RFC I will put specific reasons. Before submitting a formal patch I wanted to check if my implementation of single reads of ALS data raw values from userspace when interrupts are enabled is the right thing to do or not. Also wanted to check if my event related userspace ABI implementation is in line with IIO subsystem. I will put it into better words in the next cover letter. Can you also help me out with the git tree I should use to format the patches? As per my understanding it is the subsystem maintainer tree and the main branch but the macros and functions which you have suggested in other reviews are available in Linux mainline. Regards, Subhajit Ghosh