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 A041BC678D5 for ; Sat, 11 Mar 2023 07:16:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230162AbjCKHQh (ORCPT ); Sat, 11 Mar 2023 02:16:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45472 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229846AbjCKHQe (ORCPT ); Sat, 11 Mar 2023 02:16:34 -0500 Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 401C612C0DE for ; Fri, 10 Mar 2023 23:16:33 -0800 (PST) Received: by mail-wr1-x436.google.com with SMTP id h14so7016740wru.4 for ; Fri, 10 Mar 2023 23:16:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678518991; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=FOeXrcTnNWbTzKi6E9l84Z2v2QMvdCtKFsEt5GB4CRU=; b=Hyh6q2afJ81eWMsTciI6oeov2twf4NTSgFWhvvm3jnGh1QYJO2VXkgiAVWM8/B7g+e xjoUyK70agYunrw8KHq85mq5RsvTdveeVbqvumPIeIOoqmY8A8sWKiVqNL+MXvrOWPIH oJIvaMpyGwp4rLAxUPzZKz4g/5ETHLsw3C0wJQNFnrFAKLBUN69Vh+7Vujl2g0wOcR9d mK/9/lcxXWmOW+hkf5oGhhw/oqGRaJ2oW1tgsTevQ5P7xjriBXZZzkntKEOHw3glPhX0 MOdEEwjnXnmwr3RFSxC4I/tZjr9eRi5xNUkHwB3XlinT87hpi2P8OH/y6VxmL+yFLrS0 EBsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678518991; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=FOeXrcTnNWbTzKi6E9l84Z2v2QMvdCtKFsEt5GB4CRU=; b=Z0L454TDAs2JIMUE4T1xLn+teIw1NUzEexQa3wne9mvUa2T/UXzoElaBfnLMcH+GHY 3XityF/2AEGyVJ1nJGnT6x8/dKWCT6pJ2zifqyExoVwMqCyeA9vy0besxqbSYtQ6Hb/k aSLM+IH0ljAFd9IpJ2EK06YjK8Ybvg36zJjNSVscMmzh/TrYHAvUsezMLGc1vg3TpZS8 ER3d7b6dWBVNCOIjSBGk23qgNLAeD5cVx4ItS9Q26sJ1WcXu3qfMgsrqBhnuXfmnDPE+ WLx6Jv3iCesyjUbFrcz9lxev93Kr57KxGBPjyuPmNPk5IdJRAx4HSKwnxFR775mimO2Q oRqQ== X-Gm-Message-State: AO0yUKWBe9lZBDv1PmjBkQIpwQhVZVW3Y+XYlYSX2bjD7ze/LyXIW7a5 nnmILRDliG81Az0Yzb1j51MG35jMAgwWXuoR X-Google-Smtp-Source: AK7set/MQHjs+2HnUEPKYvtMPFzjUMd8XL/gPJgsXRh4Zdcc0tiom//uHYHVwT7zGDPiVCsnYinlMA== X-Received: by 2002:adf:eb50:0:b0:2c7:1dd5:7918 with SMTP id u16-20020adfeb50000000b002c71dd57918mr17307669wrn.28.1678518991270; Fri, 10 Mar 2023 23:16:31 -0800 (PST) Received: from khadija-virtual-machine ([39.41.45.115]) by smtp.gmail.com with ESMTPSA id s11-20020a5d4ecb000000b002c70851fdd8sm1655094wrv.75.2023.03.10.23.16.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Mar 2023 23:16:30 -0800 (PST) Date: Sat, 11 Mar 2023 12:16:28 +0500 From: Khadija Kamran To: Deepak R Varma Cc: Dan Carpenter , outreachy@lists.linux.dev, Vaibhav Hiremath , Johan Hovold , Alex Elder , Greg Kroah-Hartman , greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] staging: greybus: remove tabs to fix line length and merge lines Message-ID: References: <6e9fd119-6566-4778-899e-bc5a7ee7830c@kili.mountain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 11, 2023 at 12:35:49PM +0530, Deepak R Varma wrote: > On Sat, Mar 11, 2023 at 11:24:20AM +0500, Khadija Kamran wrote: > > On Sat, Mar 11, 2023 at 07:16:19AM +0300, Dan Carpenter wrote: > > > On Sat, Mar 11, 2023 at 03:18:04AM +0500, Khadija Kamran wrote: > > > > In file drivers/staging/greybus/arche-platform.c, > > > > - Length of line 181 exceeds 100 columns, fix by removing tabs from the > > > > line. > > > > - If condition and spin_unlock_...() call is split into two lines, join > > > > them to form a single line. > > > > > > > > Signed-off-by: Khadija Kamran > > > > --- > > > > Changes in v2: > > > > - Change the subject and log message > > > > - Merge if condition and spin_unlock...() from two lines to one > > > > > > Apply your patch and then re-run checkpatch.pl -f on the file. You will > > > see the problem. > > > > Hey Dan! > > When I run checkpatch.pl on my file, I can see that my old CHECK no > > longer exists instead a new CHECK is mentioned saying 'Alignment should > > match open parenthesis'. I understand this from your previous email. > > Should I stop working on this file and leave it as is? > > Hi Dan, > Not trying to speak for you, so please override my message if this is > inaccurate. > > Hi Khadija, > Yes. It is not useful to resolve one warning and introduce another. Tomorrow > someone else is going to try and revert it. So do not make the "remove tab" > change. I still like the merging of the split lines. It appears to improve code > readability. You can send in a v3 with just that merge change and wait for > feedback. > Hey Deepak, Thank you for the feedback. Before sending a patch v3, I think I should wait for more feedback. > Also, remember to check your change with checkpatch. There is a section about > post-commit hooks on the tutorials page. This will allow you to integrate > checkpatch as part of your git commit step and do the job for you. > > And also, always build your change locally on your machine. No new warnings or > errors should arise. > Yes I will keep that in mind for next patches. Thank you! > Hope that helps. > Deepak. > > > > Thank you! > > > > > > regards, > > > dan carpenter > > > >