Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1529657pxb; Sat, 29 Jan 2022 08:36:34 -0800 (PST) X-Google-Smtp-Source: ABdhPJw4S9C7+7dJ3LcZDyjoGY39swFLKgGekyTWrjvYEL25xJ7STiDFzhMM5k04YlJuA+z7Xigg X-Received: by 2002:a17:906:eb8a:: with SMTP id mh10mr8193773ejb.492.1643474194436; Sat, 29 Jan 2022 08:36:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643474194; cv=none; d=google.com; s=arc-20160816; b=je2ZM1H8PqM46AKffg3ppFyoRAgWpwx3HaXJz3pJm6JIq734f53twOWBbQX9ysqXNX dc3Ohr47lzDET+rto5X91TcgrcQY9LPaCsBbtIrJUQqdEaE14BvBf/mAH6bzYpkWFdSc s0qDq+QwpH1LZQ10OGUr+8JZusAWUV+sUn/nzr8PVLlJdsElnxvl4ilXBDfoBrpYs+hF 47nSKtVq+lgTktgIr2TLaAFUc2Sa7RRwNAu355DkPoWpSauP3VkgWdbHpz7Aq50DZ10M s/GoWj9SgSH6x5kHflsDrSKceVzsL9kfuB5LEsyG1MsV0UNKDznXImit3RfRtUMXlnHC XeXg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=OD6WAteNVjoEL5BdQQseFUQxBcO/VHXKit43SSCC07c=; b=GCJtB2S0eVvSb3is9BX8tCPsRwbnD9RE3tKpl80cWiffUeELNNnpiH+9v+4OXFO61o BAbDsLWd25j866cQLuKgr9n7fanMdNXn9gEAYqZUqHw5soqm7G19jqAxEJ/xLkmSeN6d Py9pOM9b5rRpvFsCPQdrK7c4vDvZnQgEAu7w0b9eiO9FwRt/Zt3xHfEQkacTzjvyXMu8 osjvS8X12QxvUmpnZXovSAOJ7RaPuMg74AuUm1VmbMO9tIeTQNZoUGEaRWb/rGqcexxk kIzsQh9x73nC1crnGbusg8zmSXpU9yGfv/Zrg3WQOxlkyZ5gcJBZzg7OgcpXms9RFsMc R8Ow== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UvUAdSj0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id qb6si4847076ejc.545.2022.01.29.08.36.09; Sat, 29 Jan 2022 08:36:34 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UvUAdSj0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346187AbiA1FbR (ORCPT + 99 others); Fri, 28 Jan 2022 00:31:17 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:59290 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237144AbiA1FbO (ORCPT ); Fri, 28 Jan 2022 00:31:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643347873; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=OD6WAteNVjoEL5BdQQseFUQxBcO/VHXKit43SSCC07c=; b=UvUAdSj08xuzeOBLLazUkp/fTI6Ude/M4yTPFV7RT/rCiaOcIDzMCXOY4egUjgxV/tXeG7 OwWXaAFr9NZ0Htx+D7RBWiHjgI/5LFDC+Abg4q9Rav/8kQcfqlx1V4RmhHCp6OnTlxJGlP XcoI0KmpbHN13jgUziSYefEMlmT4PQM= Received: from mail-oi1-f197.google.com (mail-oi1-f197.google.com [209.85.167.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-230-9XRWgXNvMReWNos8j4WXbw-1; Fri, 28 Jan 2022 00:31:12 -0500 X-MC-Unique: 9XRWgXNvMReWNos8j4WXbw-1 Received: by mail-oi1-f197.google.com with SMTP id ay6-20020a056808300600b002cf692bd758so12130oib.2 for ; Thu, 27 Jan 2022 21:31:11 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=OD6WAteNVjoEL5BdQQseFUQxBcO/VHXKit43SSCC07c=; b=PEzkdZ9PLFo+ta/SnfbIk7nLfT9WDcalPZhMJeGeoJci4wk1DMgta0ep15TjJrsJ+D tfJMQUOPVeuvWv9GvnsVmY6jFI2//HUL7ECAeDa1bE/xg49oTKloyggNooooh+DqhpEV +FFTtWjxfFyPsZ96utNgLvKdQXCWpgmjuoJV13+R3esdpf1hCfitEdD+LhqUELArhZFf v8DrrrBBjR0dECTf9LhkBCWcfM+ax2VzEJjsPZe0e26nKr+CS/Sj+13n0qGPdfAYa93R JopkeIy+08Uajv9sKA/pe9Qsyckb2vsOEcduW39129erXIelgKFCtDP2fFZ1pWsMZfC7 el8w== X-Gm-Message-State: AOAM5317Zf/OzsYYHt55wlxE56lOQ8mn2URsTEhx2zdSL303CUVDh1S0 SClNzPlTYMTz6sGFna9N2Uq8g79GRuwR0hJjX9EeEoUBRPR6OqCUl0Jrici4UU1TFUPdSyQXbE7 9dh3WNRgDyH91lckp6kivmcy6 X-Received: by 2002:aca:45c4:: with SMTP id s187mr8701061oia.306.1643347871380; Thu, 27 Jan 2022 21:31:11 -0800 (PST) X-Received: by 2002:aca:45c4:: with SMTP id s187mr8701050oia.306.1643347871213; Thu, 27 Jan 2022 21:31:11 -0800 (PST) Received: from localhost.localdomain (024-205-208-113.res.spectrum.com. [24.205.208.113]) by smtp.gmail.com with ESMTPSA id m7sm2628382ots.32.2022.01.27.21.31.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 Jan 2022 21:31:10 -0800 (PST) Subject: Re: [PATCH] scsi: megaraid: cleanup formatting of megaraid To: Joe Perches , Nick Desaulniers , Finn Thain , Miguel Ojeda Cc: kashyap.desai@broadcom.com, sumit.saxena@broadcom.com, shivasharan.srikanteshwara@broadcom.com, jejb@linux.ibm.com, martin.petersen@oracle.com, nathan@kernel.org, megaraidlinux.pdl@broadcom.com, linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, llvm@lists.linux.dev References: <20220127151945.1244439-1-trix@redhat.com> <953eb015-4b78-f7b-5dc1-6491c6bf27e@linux-m68k.org> <5554a75f65fddab4de60d61fd503fe73773dafbb.camel@perches.com> From: Tom Rix Message-ID: Date: Thu, 27 Jan 2022 21:31:08 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <5554a75f65fddab4de60d61fd503fe73773dafbb.camel@perches.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/27/22 6:43 PM, Joe Perches wrote: > On Thu, 2022-01-27 at 16:32 -0800, Tom Rix wrote: >> On 1/27/22 2:47 PM, Nick Desaulniers wrote: >>> + Miguel (the clang-format maintainer), Joe (checkpatch maintainer) >>> These criticisms are worth reviewing. >>> >>> On Thu, Jan 27, 2022 at 2:38 PM Finn Thain wrote: >>>> On Thu, 27 Jan 2022, trix@redhat.com wrote: >>>> >>>>> From: Tom Rix >>>>> >>>>> checkpatch reports several hundred formatting errors. Run these files >>>>> through clang-format and knock off some of them. >>>>> >>>> That method seems like a good recipe for endless churn unless checkpatch >>>> and clang-format really agree about these style rules. >>>> >>>> Why use checkpatch to assess code style, if we could simply diff the >>>> existing source with the output from clang-format... but it seems that >>>> clang-format harms readability, makes indentation errors and uses >>>> inconsistent style rules. Some examples: >> Problems with clang-format should be fixed, I'll take a look. >> >> I was reviewing this file for another issue and could not get past how >> horredously bad it was and really did not want to manually fix the 400+ >> formatting errors.  I will drop this patch and use the use these files >> to verify the .clang-format . > I think this is more an issue with clang-format than with checkpatch. > > If you have specific issues with what checkpatch reports for this > file (or any other file), let me know. Yes, I agree. Its a clang-format problem. I will be looking to minimize the .clang-format settings to only those that agree with checkpatch. Then add settings back in later if their problems can be worked out. Tom