Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp217806rdb; Thu, 21 Dec 2023 07:20:26 -0800 (PST) X-Google-Smtp-Source: AGHT+IGApJAFXeLBtqfagwJx+p9oOpvgedGV6MGnA8QOfxi8/xNg69yXHTO5tfZViUJCdnn5CpBz X-Received: by 2002:ac5:cdcc:0:b0:4b6:db0f:8176 with SMTP id u12-20020ac5cdcc000000b004b6db0f8176mr547284vkn.6.1703172026452; Thu, 21 Dec 2023 07:20:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703172026; cv=none; d=google.com; s=arc-20160816; b=jyuFxYQXaUpCK5NzOWJZR/gWMXO6OaG5BOGj4vJuoc+oJjJ/Q6IHqfrYRF6awXwLFI p94JKNe9JDmjDMh7RgEoO2bZDoxAugVJS98LBLcyjfXTlktEiha156Wlh3fLskXCjZE/ YKys4Uu4JiV0rL+qr5I031cEdwNqyB0wGCWw/l2yyfURXFQSDsNUe/LdN7Kxhh16zOPJ 8w//ClFE8tsZjuY5jqR217tEY/hMEOGYvfsNUd65YOJkk0zgrk/Ss4tIFWN2EJiR/zlU ZYmQUFSzwNuCxt05YJxeTiqRFCci//pd/SxmFMFHSRLqmnxofM+M2cwqzcPLLVH+g52r 7Svw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:list-unsubscribe:list-subscribe:list-id:precedence :message-id:date:references:in-reply-to:subject:cc:to:from :dkim-signature:dkim-filter; bh=M5C3Amum1S0G/drP7vUNUyz31la15iZxUnl93TvSwgA=; fh=axJPchXL66dKPtpPfRcUY3ZEO1E0bmX7d3Eyz7uc+uU=; b=Yyyx4Wbd7tJX2xYGT7iuQcz7f8xUFveF1t3WPw7WX/yBpj3neKMDEKvgvuWw2vok+v Q8td/q2z/nHOGa0RZ/Dmc+j704iTFpyENb0dGqxugbuFteSYNYb037pjPPEoKqWHIA5W lXWbchHmUjwUl2yZuyw4copcUu0Y/WHlS145kSnK6lIbNU+5rbaF6uIHeO8SWc8985Uv I8wtq+7C0a67Aml5kgKE1SwnXww0hhVR9WbRn95rIhAXTSFoYf2GhVdpk95lZ8ywx26P swEfueBptdckKq/LWRz8rMt0aDZfKE0Q95pcqdyjWQglt6+oMfp1DE/+s3rlCLsQYiJl /rig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lwn.net header.s=20201203 header.b=Z58dPuY6; spf=pass (google.com: domain of linux-kernel+bounces-8635-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-8635-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lwn.net Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [147.75.199.223]) by mx.google.com with ESMTPS id d25-20020ac5c7b9000000b004b31a540c56si434472vkn.305.2023.12.21.07.20.26 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 21 Dec 2023 07:20:26 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-8635-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223; Authentication-Results: mx.google.com; dkim=pass header.i=@lwn.net header.s=20201203 header.b=Z58dPuY6; spf=pass (google.com: domain of linux-kernel+bounces-8635-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-8635-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lwn.net Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 2DABA1C2427A for ; Thu, 21 Dec 2023 15:20:26 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 70E044F884; Thu, 21 Dec 2023 15:20:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b="Z58dPuY6" X-Original-To: linux-kernel@vger.kernel.org Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) (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 1E7BC539E4; Thu, 21 Dec 2023 15:20:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lwn.net Received: from localhost (unknown [IPv6:2601:280:5e00:7e19::646]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 198847DA; Thu, 21 Dec 2023 15:20:15 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net 198847DA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1703172015; bh=M5C3Amum1S0G/drP7vUNUyz31la15iZxUnl93TvSwgA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=Z58dPuY6bDCSdpULMcvf2KAM/zh0Tbd23dXMxLow6IEZzdI67MaFxWKIR/OZOLXqm HXpfXEnoVOUJFWMka2soRTu02/eXPZT1vgLO9ZHgDlWnS3eojZmYcPICgc8Y4ZC6nT 0Pc2NvGy48PalQjFrR7C728h4E3q9iP0Ll9pBznDjfTfsuF2TWEjoUnDsSJwi7pivG rhaw00HMW7WskzZMWUUif9MNFSi9x+hBjks2bHoA8VVvHMw1Pi7ASjg8sQ49u3XaZL 7eQOoviOMcI6CeZA+T2hd8/o8ZfAW6cmEMuNBdUcMx+ZyzqwLEDWd6Bx8W5vR2tbsh UUwOagYyy5q5A== From: Jonathan Corbet To: Vegard Nossum , Randy Dunlap , linux-kernel@vger.kernel.org Cc: Mauro Carvalho Chehab , linux-doc@vger.kernel.org Subject: Re: [PATCH] scripts/kernel-doc: restore warning for Excess struct/union In-Reply-To: <93e1b9fa-c447-4f7d-9dc7-825ebe9e1cde@oracle.com> References: <20231214070200.24405-1-rdunlap@infradead.org> <875y0zqvjr.fsf@meer.lwn.net> <93e1b9fa-c447-4f7d-9dc7-825ebe9e1cde@oracle.com> Date: Thu, 21 Dec 2023 08:20:14 -0700 Message-ID: <877cl7a8gh.fsf@meer.lwn.net> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Vegard Nossum writes: > On 15/12/2023 17:28, Jonathan Corbet wrote: >> *sigh* >> >> This adds nearly 600 new warnings. Anybody gonna help fix them? > > I think in the vast majority of the cases the fix will be to just remove > the offending line from the kerneldoc, so it's not particularly > difficult, mostly just overhead from the patch preparation/submission > process. > > I'd be happy to take a stab at it -- I think we could even script most > of it. Respond here, I guess, if anybody else wants to do some so we can > split it up. It's mostly done; I've gotten it down to under 200 and sent patches to make the changes. Randy is working on it too, I know. It's not always just deletion, but the fixes are usually pretty straightforward. > On a related note, it might be useful to have some kind of "status page" > somewhere on the web for the docs where you can see a list of unresolved > documentation warnings in mainline/docs-next/next without having to do a > local build first (as a way to solicit contributions). I suppose, but how do you know you've properly addressed the warning if you don't do a build afterward? I don't see that saving a whole lot of effort, but maybe I'm missing something? Thanks, jon