From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zytor.com (terminus.zytor.com [198.137.202.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4DFD22DF134; Tue, 18 Nov 2025 19:11:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.136 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763493103; cv=none; b=Av1xJjnfQ0rtlxGHFOVSzPImahHiZAxBUNU5n8tbjjDFB1ATHiU0kX4Qu9f3l0URBEsk2nvw6y7yAP+liISUZO6V/X2IIncqesJAGGdhxgJVCGw+Ziqs8T0PLxpTVyk+h98YemdkyJ+h5M7UOq7Jcmu6PSezga2zn1lKknxtl18= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763493103; c=relaxed/simple; bh=wmt2ufpsSU3ouyeaDMQzjmquVyGx8emmZiWQD0l4Yrk=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=K8PKBpYbvCN52/NxfI/cEJ//PrCioafq2sqPTecEjJkqnzvPdhinX7DJjBAnWte+Gg/oW381W9OAzW7fkgnn1LjaUn9PFvmbJLsN3k2bAOasH33iwPQP25KVglITn2eRhfeWreZ6olkn6qW7P3zj8CaH4V6rGe8nsg2A/ZU/Kx8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com; spf=pass smtp.mailfrom=zytor.com; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b=pYodApqe; arc=none smtp.client-ip=198.137.202.136 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zytor.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b="pYodApqe" Received: from [IPV6:2601:646:8081:9484:7ccc:663a:75c9:3b5f] ([IPv6:2601:646:8081:9484:7ccc:663a:75c9:3b5f]) (authenticated bits=0) by mail.zytor.com (8.18.1/8.17.1) with ESMTPSA id 5AIJBE9T989824 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 18 Nov 2025 11:11:17 -0800 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 5AIJBE9T989824 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2025102301; t=1763493082; bh=3omHpCluL+9JXWDs65PxMcE9qeJS+kGriI7Y0AjSgG0=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=pYodApqeTJxTlGe88vHjRj+RQbiqeZg+gv5WXWqNQ2ckP0oJzaJubjsCKmjZapDCy fLl0s157XptGX6Xj7brJcAmMTJkXhle57352FsysZILkxnrIW4rOxxR9qv0CWTZzkG d1rPNmwHR+FZLTAsD84p7hKmORrFLdmeSmpnLi6q2exL2BdYv5KpqWc79cHWul5nuO /9CdU8bkj7SnIXgJkNZOubdc2UksBn1wJ9BRu27dSxL45hIQbkR0Htjo1OBzZXEqNr rgRUVfxXAOUaaSKvLLZK97LntUq75txLd5yG3/8CNgvq/QuDIAg83aEHmxjhH7AK8x GIWunIFGrQb9g== Message-ID: Date: Tue, 18 Nov 2025 11:11:09 -0800 Precedence: bulk X-Mailing-List: ksummit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Clarifying confusion of our variable placement rules caused by cleanup.h To: Linus Torvalds , Bart Van Assche Cc: James Bottomley , ksummit@lists.linux.dev, Dan Williams , linux-kernel , Dan Carpenter References: <58fd478f408a34b578ee8d949c5c4b4da4d4f41d.camel@HansenPartnership.com> Content-Language: en-US, sv-SE From: "H. Peter Anvin" In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 2025-11-18 10:38, Linus Torvalds wrote: > > Now, we currently don't use __auto_type very much outside of macros > (and there we often use "typeof(x)" instead for historical compiler > reasons), but I suspect we probably should. There's a patch floating > around that makes it more convenient with a > > #define auto __auto_type > > because the historical C 'auto' keyword has been so completely and > utterly useless. > Indeed, and this matches C++ and C23. The only thing about it was that it got to be fuzzy the best way to upstream it. Do you want me to send you the patchset during the merge window? -hpa