Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp5906394rwi; Tue, 18 Oct 2022 05:54:25 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7EBfS/TpEXS9nD9S6y8pdrWGgbtH7Vrn7F3JbG665RLbo9Lo9ryIlpxJfeAxlIqYZw735z X-Received: by 2002:a17:907:2712:b0:78d:a223:729b with SMTP id w18-20020a170907271200b0078da223729bmr2269106ejk.443.1666097665148; Tue, 18 Oct 2022 05:54:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666097665; cv=none; d=google.com; s=arc-20160816; b=NSgV+nAemcsp/BrN56eamad/oNmc6hLiimNAmtSegWEK0spar8hf0a3a271JzJh93m 8G34L8mGfuhM6h5Hqx+HaFbd+pJljpq/tYdmEmtV/8vkblE643eFTRq200o7I29tve6E XE+XaE5Y5N+kPzbwKfmfQVZ4hSfVKFwfEXRSbZ5vRJpYL+SYKaMIdNyK143uOOytOPLc W4zoNqtVaYY16IyxTbTe6Yc4dY5AUBV6IHtyzoSLKw39NdlZoUp/JaoxV3Jt70AsNxsk D6qAQ50DosnKuRcVMm8wV245+8QCio4PcJ0ISWFl1ZdmpypgFp8MzZUrxWeXknsRcW6H lkgA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:references:message-id:in-reply-to :subject:cc:to:from:date:dkim-signature; bh=iX2U8THf+pquiaMR5M0K15dQE8WhWpHiv6AT0EQcZUY=; b=vKFa0YsnfKOIWMC7YTUpEDBu/d3O93ZNFvC5BJY90npaiSl8BJY9f2oYtc4RNaZHIu chCFY/IkJ7U9ar0qJ/2IRtJSeulJXfeXGHmGVS3SuqicThWLkH2b7ZsRjAxlx60dsF9X iQH3pr2N1pObDYbLh8vb89Zg4ZvOxfW1urjfiVypeMhDQm8CDAmbIlOqEZag1Cx4Lacs F6Igdbp7XlbN+oKT6EmOTDeeCH6+zkFwDsAO5DUA7VVRTMx6om8JlaEcwj4Ep0OLaFfS XnPxp4dHzfUvU9MJkd74VgUGLD4yUNfSpXIS9Tzfk1ia42h56S5wip2jr2cabo2t/UsB CEkg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@inria.fr header.s=dc header.b=XknR4xUn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=inria.fr Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y3-20020aa7c243000000b00457263f9ee0si9892864edo.93.2022.10.18.05.53.58; Tue, 18 Oct 2022 05:54:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@inria.fr header.s=dc header.b=XknR4xUn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=inria.fr Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230167AbiJRMwZ (ORCPT + 99 others); Tue, 18 Oct 2022 08:52:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49896 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229871AbiJRMwY (ORCPT ); Tue, 18 Oct 2022 08:52:24 -0400 Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C2D8EC34CD for ; Tue, 18 Oct 2022 05:52:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=iX2U8THf+pquiaMR5M0K15dQE8WhWpHiv6AT0EQcZUY=; b=XknR4xUnCb36LgqEyYpiwSqxy0Urej3cmaVjBncToBcE5jEld1QWiBYx v0GiNugIsuobfs1zyW/ZeuC5hW48DxSjnTPUTIFrv4Kno0arfuaQqAEv0 jbV4nfUX8wbV9VT3Jf3toRTCcnvQLdvDymtLFR38lZj6YlHheifW7wL6Y c=; Authentication-Results: mail2-relais-roc.national.inria.fr; dkim=none (message not signed) header.i=none; spf=SoftFail smtp.mailfrom=julia.lawall@inria.fr; dmarc=fail (p=none dis=none) d=inria.fr X-IronPort-AV: E=Sophos;i="5.95,193,1661810400"; d="scan'208";a="65749943" Received: from dt-lawall.paris.inria.fr ([128.93.67.65]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Oct 2022 14:52:21 +0200 Date: Tue, 18 Oct 2022 14:52:21 +0200 (CEST) From: Julia Lawall To: Deepak R Varma cc: outreachy@lists.linux.dev, gregkh@linuxfoundation.org, linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org, kumarpraveen@linux.microsoft.com, saurabh.truth@gmail.com Subject: Re: [PATCH v2] staging: most: dim2: read done_buffers count locally from HDM channel In-Reply-To: Message-ID: <80696861-c73f-cdb9-b4e1-36c29ece78bb@inria.fr> References: <1e2a71a9-4ac5-96f3-b875-a063ff62f3ad@inria.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 18 Oct 2022, Deepak R Varma wrote: > On Tue, Oct 18, 2022 at 09:39:08AM +0200, Julia Lawall wrote: > > > > > > On Tue, 18 Oct 2022, Deepak R Varma wrote: > > > > > The done_buffer count is already available in the hdm_channel struct. > > > Calling dim_get_channel_state function to source this value out of > > > the same structure is unnecessary. > > > Further, the second parameter struct dim_ch_state_t to this function > > > is filled by using the hdm_channel inside the function. This filled in > > > variable is never used in the caller and can be altogether removed. > > > So, a call to dim_get_channel_state function in this context also > > > deems expensive. > > > > Thanks for the rewrite. > > > > I find "source this value out of" hard to understand. > > > > I would have written something like the following: > > > > The function dim_get_channel_state only serves to initialize the ready and > > done_buffers fields of the structure passed as its second argument. In > > service_done_flag, this structure is never used again and the only purpose > > of the call is to get the value that is put in the done_buffers field. > > But that value is just the done_sw_buffers_number field of the call's > > first argument. So the whole call is useless, and we can just replace it > > with an access to this field. > > > > This change implies that the variable st is no longer used, so drop it as > > well. > > This is really well written. Sounds much structured. Now my own log message > sounds a little random :) > > Is it okay for me to use your verbiage as is in my patch log? Yes. julia