Received: by 2002:a05:6a10:d5a5:0:0:0:0 with SMTP id gn37csp4955294pxb; Tue, 5 Oct 2021 14:09:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzwEajfLC/IRr5Rv/l+ZuYJa0RHfMXEhPboTqXLaGEewjJfCL+JtwTotkU/VATCcWYfmF6x X-Received: by 2002:a05:6402:5245:: with SMTP id t5mr25722733edd.329.1633468158700; Tue, 05 Oct 2021 14:09:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1633468158; cv=none; d=google.com; s=arc-20160816; b=Dc1/N9NLAuV6DHnkmG1eQhSgDDa2ErtqWF1pSfHqaUp29VXaxrC6yPNFeABayON66P /Im00gOmJSBSh/QL7gipy/SrhUhjrQSjxAIixxGrz/vAhATYTKMmuyePbAqszj9iBGEG ebAKL9TRlTEIo7tLYGdmlViZMTVHEGUM1MhZCfEsATFayxG5Ct6TFIqTg1hCjaZOrNvZ +WTJYNc9l81K0uqaiJrZ4LZCp246da2NiFVd4+suovLZDqhpLkEQeeoUWGKkMA6ZKVJh n5m63RaILyCE5J7wUq8yrqv5VWRR7/9s0IJGYtev99PIrCmg0T0Q07sTRsG8O6o3begZ 8wvQ== 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=KST/WPSmdw0svMLJ3wYMc8jnDk12plOyqzdd74AcXyM=; b=aoSMB6MORcjmJZxvZ4MZPRv56EsiuXxA9Wlxq0E0nk4Y6MdPI2DJmtxIkF+/eAG0x9 v1sDhD4uoIU/mr0LGPZOovgcZifaWMpIKdCKkePjVma8NForvqrVf7wBOXTjgGlClv6B GGoh09NPMKuxVbrk9wNsi93cEAu5cNycvsM+x4+2G0UFwU1hlR9+oVOvWykJkV809KEs wMOWrh7A0I0/Ax4h8Z93t4idKV5XaFFRVaC4xA5nk4Z9NlH+GwHeuffCAa0SupBavOtj WPRMI13hbKTNg4WsfNm9A0RM9k9KhnzY7zaLjiWyMY89Lpfufc7Ynvp5t5h3SEObJ7Tm scVg== 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 b11si13207615edm.525.2021.10.05.14.08.54; Tue, 05 Oct 2021 14:09:18 -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 S236610AbhJEVHN (ORCPT + 99 others); Tue, 5 Oct 2021 17:07:13 -0400 Received: from mail.kernel.org ([198.145.29.99]:34020 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231322AbhJEVHM (ORCPT ); Tue, 5 Oct 2021 17:07:12 -0400 Received: from gandalf.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 EB00E61139; Tue, 5 Oct 2021 21:05:19 +0000 (UTC) Date: Tue, 5 Oct 2021 17:05:18 -0400 From: Steven Rostedt To: Linus Torvalds Cc: Jan Engelhardt , Mathieu Desnoyers , Rasmus Villemoes , linux-kernel , Paul , Josh Triplett , Lai Jiangshan , "Joel Fernandes, Google" , Pablo Neira Ayuso , Jozsef Kadlecsik , Florian Westphal , "David S. Miller" , Hideaki YOSHIFUJI , David Ahern , Jakub Kicinski , rcu , netfilter-devel , coreteam , netdev Subject: Re: [RFC][PATCH] rcu: Use typeof(p) instead of typeof(*p) * Message-ID: <20211005170518.07bd5c4c@gandalf.local.home> In-Reply-To: References: <20211005094728.203ecef2@gandalf.local.home> <639278914.2878.1633457192964.JavaMail.zimbra@efficios.com> <826o327o-3r46-3oop-r430-8qr0ssp537o3@vanv.qr> <20211005144002.34008ea0@gandalf.local.home> <20211005154029.46f9c596@gandalf.local.home> <20211005163754.66552fb3@gandalf.local.home> X-Mailer: Claws Mail 3.17.8 (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 Tue, 5 Oct 2021 13:45:52 -0700 Linus Torvalds wrote: > If there was some clean and simple solution to the compiler warning > problem, that would be one thing. But when you think you need to > change core RCU macros, or lie to the compiler about the type system, > at that point it's not some clean and simple fix any more. At that > point you're literally making things worse than just exposing the > type. Fine, I'll just create a separate header file with all that is needed and add it to the include. At least that way, it doesn't muck up the rest of the header file. -- Steve