Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp3447402pxb; Mon, 4 Apr 2022 17:16:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz/LVRTli2QULAzV4lifhF37n+U6uj0FhqvErYsH3oua5+TSFceZxx/zK9E0kUhh4x+Jyw1 X-Received: by 2002:a05:6a00:114b:b0:4f7:915:3ec3 with SMTP id b11-20020a056a00114b00b004f709153ec3mr849996pfm.8.1649117802824; Mon, 04 Apr 2022 17:16:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649117802; cv=none; d=google.com; s=arc-20160816; b=G3iTkxzCJpaW+NUdUG4zJaDT1bYTenGcDvcsJAW3q2iN7R48sHfdPrlrUCxF2QyqjD 8co3G/6xZvZgwMdNj+wv8RDEsjiKS5+3MFGXyGZPUS/d2hbrBaQl99CuQcF32XLGZ3tK KKeIZ4zFTmE661uVFW4c9uV0UlC84WYukYKTsNkOKznwVyuZZGwLrYEKcG67iPb3b5Il 95pJXSJdEKWcYMv6hM73/qJNZy+6Uou8igWAwzAO6zWEsiyfY4L4pCxb/n1Zaq0bO4aS tNi/WLkHzvw2TdvHrXQw4IuYtHwIZN2/zm3YVfs1K2dlDcGT3oeTPYNd/7pyru3o3roA Z2Bw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=y9ueE08O4hgLJ/etsVdj1Kl8Il5FNA2+FWPSFvQRrPk=; b=u7vuy/Qbo6k9RdjklL2TPrO/2/iRsYiNLPnMk4eO/ycbwcLeTDUwZC/2A6lY9ofxK4 DsxrehwG3sYdQgCK0UyF2hPQrfQhGdPK8BW0T1wLdL/oMVjEN/h4j8GeagUb1zE6cQvX oTiqINS6L3byZgjtJZsMEaH/8DWaULPxOC9UGumxZ3piXqbFo98WjSTwN8cpg0L39/RJ IUEsQ9MSRRhmEQtHeBAMIO2UKgCcDqqn6ByWJY2PyPOajToY9qff3txw9TTMbR0Qq80M 5oem0YUXXYPrlcXm+laxuALtT7lV68aD4goI7VvRo8pNPAtyG54jjhK4ZKj9VVlREWvW wDmA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=U+HajK7v; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id d1-20020a170902854100b00153b2d16493si10693038plo.155.2022.04.04.17.16.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 Apr 2022 17:16:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=U+HajK7v; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 5D5D838DA1; Mon, 4 Apr 2022 16:44:42 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1359575AbiDCRCL (ORCPT + 99 others); Sun, 3 Apr 2022 13:02:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58584 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234629AbiDCRCK (ORCPT ); Sun, 3 Apr 2022 13:02:10 -0400 Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E41EE33A0E for ; Sun, 3 Apr 2022 10:00:13 -0700 (PDT) Received: by mail-lj1-x235.google.com with SMTP id g24so10096120lja.7 for ; Sun, 03 Apr 2022 10:00:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=y9ueE08O4hgLJ/etsVdj1Kl8Il5FNA2+FWPSFvQRrPk=; b=U+HajK7vqk1UVA1fsIaKeJKFZd7cfzVEcwM4KyUoZ2V0Ugn+cZGoZLPMP0MtdaBWRS alyBTpxOK/kPBbB5H+BZ2edC9isgxq9HwRKLHFEe9+wHKvRCBd8A7EIafe5zLl6VBgX2 5GpqjuD2PLXR72sXVIlqxmMGocx+ENmc+txeLLXT+WZlzKBAyjzuIo8YHi7KkfMBGPGt qmhnXv8IOnuyxamhdlB+PENbk9pErGvYi7b/v7sJ+hZpePT1DkGvMIqoV2gVXkQaQtL4 u52lNn2EHzCx5x6Bj/vAvxqHRSYdUVp7PhscZGCHsSakft2rgstcYHKmdGc7fwFIzHb7 75Jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=y9ueE08O4hgLJ/etsVdj1Kl8Il5FNA2+FWPSFvQRrPk=; b=Q8LxBn7KCkb/UFCAXYl2F+3qzthwuhy0wXM1YYmnkNdHaVeKC9zjxgPFBihi5vLBww 3S72CeAQxbvrQs4u8yOx4IvGpQ3HwYwhCaApa7fu4hGBCz1xwLuWEGEs1GhlUbaw/E01 9mVJPv+X0eiAuK1pLUVri1uoeu89+FMXdlnji5AM6zyM4LgE02CBXpY3rXxtVTseaj5I 81jWPB1ev5icR72xAKfqId7fkd/AZIVzmasBIY4snpz/4TXerBX+xRxqypN6U16JRfE0 aOKHMOksHWKmhc+Nu8rIl7QyHiOFl7BDUzUrW1VX2f/ZilknZ0obDmYG+sa6iYv/Rnwj sayw== X-Gm-Message-State: AOAM533FIVfDSYTCuSjWXMDIitvNgM9/d7sXahgFFInfPtCorW6nqVOQ f3bfr+w8z6DGiqGCRHe70iirhWcJGYEd1aBON9QzTdfRtZjpowzC X-Received: by 2002:a05:651c:1507:b0:249:83b4:9a27 with SMTP id e7-20020a05651c150700b0024983b49a27mr20023362ljf.24.1649005203378; Sun, 03 Apr 2022 10:00:03 -0700 (PDT) MIME-Version: 1.0 References: <20220403155111.GA333187@euclid> <4ccc9ac3-c542-cd32-0cbb-7cdabbf0dbf9@gmail.com> <3e1dfdde-d9f3-9e16-82a6-7b5497981bdd@gmail.com> In-Reply-To: <3e1dfdde-d9f3-9e16-82a6-7b5497981bdd@gmail.com> From: Sevinj Aghayeva Date: Sun, 3 Apr 2022 12:59:51 -0400 Message-ID: Subject: Re: [PATCH] staging: r8188eu: simplify control flow To: Michael Straube Cc: Pavel Skripkin , Greg Kroah-Hartman , linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org, outreachy@lists.linux.dev Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no 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 Sun, Apr 3, 2022 at 12:43 PM Michael Straube wrote: > > On 4/3/22 18:29, Sevinj Aghayeva wrote: > > Ah, I see. You run it on an email file that contains the patch. I > > could reproduce what you saw when I ran checkpatch without any options > > on an email file. But my usual workflow is to modify a file, e.g. > > rtw_mlme.c and then run "checkpatch.pl -f rtw_mlme.c", in which case I > > cannot see the "Alignment should match" error. So it looks like if you > > do not specify -f then checkpatch.pl enables --strict option. > > > > Hi Sevinj, > > I'm also not a checkpatch expert, but on my system this works without > --strict too. I applied your patch to my local tree and get: > > /scripts/checkpatch.pl -f drivers/staging/r8188eu/core/rtw_mlme.c Hi Michael, That's odd. I don't get any CHECK messages if I run exactly the same command as above: $ pwd /home/sevinj/k/staging/drivers/staging/r8188eu/core $ ~/k/staging/scripts/checkpatch.pl -f rtw_mlme.c | grep 'CHECK:' | wc -l 0 I have to specify --strict to get CHECK messages: $ ~/k/staging/scripts/checkpatch.pl --strict -f rtw_mlme.c | grep 'CHECK:' | wc -l 167 I don't know why that is. I'm on Ubuntu 20.04 and it looks like I'm running checkpatch version 0.32: $ ~/k/staging/scripts/checkpatch.pl -h Usage: /home/sevinj/k/staging/scripts/checkpatch.pl [OPTION]... [FILE]... Version: 0.32 > > [snip] > > CHECK: Alignment should match open parenthesis > #1638: FILE: drivers/staging/r8188eu/core/rtw_mlme.c:1638: > + if ((p->PMKIDList[i].bUsed) && > + (!memcmp(p->PMKIDList[i].Bssid, bssid, > ETH_ALEN))) > > [snip] > > You can also run checkpatch on the patch files (without -f). > Then it's easier to see if you introduced new issues. > > regards, > Michael -- Sevinj.Aghayeva