Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp945937pxv; Thu, 1 Jul 2021 13:01:13 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwMYFZIY/LA2UrlElwgY2yxYw5WJT8dPsgA9OI1xuBUdizSQ3BPbPlsonqOfIMoyNo5RdKy X-Received: by 2002:a05:6e02:921:: with SMTP id o1mr850391ilt.57.1625169673549; Thu, 01 Jul 2021 13:01:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625169673; cv=none; d=google.com; s=arc-20160816; b=PYrmRBtjbXVdmhwNWdakTBx5teeRY3fxIRu8OIc4TIbYI01lLtU4J0F4S1A6P5hCQW YXpbjwgUpKqzcUwaLb6KkOSKKSJGNWSEpO+ZlsfAYB30ZEhrj1zamqDWh1P7q//8Vzpu aXWNxQdjJx6w9MC41S2vVhUHwtMTVkYbes9RUlhEKaT4lE23v2xj+OFCgugqQCDOO8uv Zefhta5Gp9NAf0BF5YuxRh5cSq+o0m9+1lLHytD4rQzAtcyhRVDhl8WcR7y9DyK6OpRM D+3/N6P8nvQfzTowy/fXmt9SoXqKNT5WQ+kRPLW2BBP4/Mx1TwXxElh39q8ycF+1wrnm WI8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=srmHl/4w9iQHX+8RVHsKzF9XSMlN7OzRAaZaPKFg2x0=; b=bPsVHU5XW5V0KqNgyNtLuUYE3UQc12pd6DHl92pTWhm15h/Py7gO51I6V9NQvi9mGt 4lVI7DnKCSma8pNE8Bp5QJZ02k15jIlRDvnLITbGUgTFrNCWPQy2Q/u3xpVaFaG0YJ3C Nw0dMTY4q2VcZFvFoYrHRV0Dpj4VTHLZSfVaXohW0uMc+JTzRUaj5++zxCFTnNYYc0J4 ZTAqq6dOuTK8Op4rlqcw/rHR+bkkZ1/ut3NKBBOCAsQsVct7z1H4QVjhfGMHqbxGEx8e SH4QwTOJDTpFvv775ZDgPmqZWUUA399oZth7x53qDrqMPegGLTe4cf2W9/YX9OiDsv9r vVvA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l15si885009iok.34.2021.07.01.13.01.01; Thu, 01 Jul 2021 13:01:13 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231726AbhGATxe (ORCPT + 99 others); Thu, 1 Jul 2021 15:53:34 -0400 Received: from mail.kernel.org ([198.145.29.99]:49922 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229894AbhGATxe (ORCPT ); Thu, 1 Jul 2021 15:53:34 -0400 Received: from oasis.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 8DDF360FF2; Thu, 1 Jul 2021 19:51:02 +0000 (UTC) Date: Thu, 1 Jul 2021 15:51:00 -0400 From: Steven Rostedt To: Joe Perches Cc: Paul Burton , Joel Fernandes , linux-kernel@vger.kernel.org, Ingo Molnar , stable@vger.kernel.org Subject: Re: [PATCH 1/2] tracing: Simplify & fix saved_tgids logic Message-ID: <20210701155100.3f29ddfb@oasis.local.home> In-Reply-To: <51babd56c2fe53ba011152700a546151@perches.com> References: <20210630003406.4013668-1-paulburton@google.com> <20210701140754.5847a50f@oasis.local.home> <20210701142624.44bb4dde@oasis.local.home> <51babd56c2fe53ba011152700a546151@perches.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 01 Jul 2021 12:35:29 -0700 Joe Perches wrote: > C99 comments are allowed since about 5 years ago. Really, I thought Linus hated them. Personally, I find them rather ugly myself. The only user of them I see in the kernel/ directory appears to be for RCU. But Paul's on the C/C++ committee, so perhaps he favors them. The net/ directory doesn't have any, except perhaps to comment out code (which I sometimes use it for that too). The block/, arch/x86/ directories don't have them either. I wouldn't go and change checkpatch, but I still rather avoid them, especially for multi line comments. /* * When it comes to multi line comments I prefer using something * that denotes a start and an end to the comment, as it makes it * look like a nice clip of information. */ Instead of: // When it comes to multi line comments I prefer using something // that denotes a start and an end to the comment, as it makes it // look like a nice clip of information. Which just looks like noise. But hey, maybe that's just me because I find "*" as a sign of information and '//' something to ignore. ;-) -- Steve