From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E441EC47422 for ; Mon, 29 Jan 2024 11:14:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Type:MIME-Version: Message-ID:In-Reply-To:Date:References:Subject:Cc:To:From:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=M/YNNP3dQ096/ctf1cO2Y/8JuPGQvKQjrgzL4GgK9KU=; b=ZvWgLY4vA5ziQZ88id0rdQM+05 LEQ6XfWjQg/5HzQ3WkMrBxof1FSITCTdrYs9LlvvihaRDuN1ssA5sstsZubbaxnIay+Fqy6/6bF4Q nSH+4PK6IueWumGTfYUgcEKs6De2lsmElNLCh0LhrF1PQVJY6IcezBjcNAuDUgfnV+USBxhGO8zOK 5Clr427Wy9zCSWFuaDDuqleYLzXQi8ieb3ObsjWCwDH7DdH99R73u0+SVHOBbVGmv9rJX/zCikOC7 tYyvu0E/B1VbHNe0sfBfPXxx+xIFHUmXLGpCDSlJfNsVnV1PxJgUrbOkjdSGkJ8F0GdzQjuNi9dJ7 Gvps/QfA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rUPbC-0000000CN3p-1sgR; Mon, 29 Jan 2024 11:14:46 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rUPbA-0000000CN3D-0oEV for ath11k@lists.infradead.org; Mon, 29 Jan 2024 11:14:45 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 5E8FD620CD; Mon, 29 Jan 2024 11:14:43 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 18052C433C7; Mon, 29 Jan 2024 11:14:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1706526883; bh=WmE0fsg1x9uaRKxDdJFE55N2p6ZINp1Yi48GoUlIIsc=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=AJX8NpXlwvyEcyqETHycRIfU3BmA3IJvX2EJsIH3Gx9wsO+hpJHCwvbBJv32e0dq5 JJPI+NDMTp6rTf85q2yrnQbTLr+O/KBdG/im06hpX1g2L6694mR12w0sUJn9gBdyb5 9LjJ5ds6YmXZyyFIQl7G7kqsnDDYweO25nuZheOQOOMd2Nt/+ScABH7J9PLdq4dATI R0+JbPVCDlIM/HIs2XrREgL7/armESBa1z65Pwo5fIDkVQsNmMyhiK/Xw2q15aCXQa kQeRE89hu0SLGHDhtTLQ8qHZaRgWKfpUMt/y9FSI1D/0Om13MA3JoNWrCQ0SC31MrY plnmHKajOTBYg== From: Kalle Valo To: Jeff Johnson Cc: , , Subject: Re: [PATCH] wifi: ath11k: document HAL_RX_BUF_RBM_SW4_BM References: <20240111-document-hal_rx_buf_rbm_sw4_bm-v1-1-ad277e8ab3cc@quicinc.com> <874jfg7xm4.fsf@kernel.org> <875xzq526o.fsf@kernel.org> <87ttn0xc9y.fsf@kernel.org> <9c321dfc-f10d-4092-a1cd-30952e4da695@quicinc.com> Date: Mon, 29 Jan 2024 13:14:38 +0200 In-Reply-To: <9c321dfc-f10d-4092-a1cd-30952e4da695@quicinc.com> (Jeff Johnson's message of "Fri, 26 Jan 2024 09:05:26 -0800") Message-ID: <875xzcxug1.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240129_031444_358755_A09F8CFF X-CRM114-Status: GOOD ( 13.14 ) X-BeenThere: ath11k@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "ath11k" Errors-To: ath11k-bounces+ath11k=archiver.kernel.org@lists.infradead.org Jeff Johnson writes: > On 1/26/2024 8:58 AM, Kalle Valo wrote: >> Jeff Johnson writes: >>> They have the same problem I'm trying to fix ;) >>> % scripts/kernel-doc -Werror -none \ >>> $(find drivers/net/wireless/intel/iwlwifi -name '*.[ch]') >>> ... >>> 322 warnings as Errors >>> % >> >> Ouch. But I'm surprised why nobody has reported these before? Are the >> kernel-doc warnings ignored by everyone? > > There are folks who use the kernel 'make' command to build the > documentation, and report issues from that. But my understanding is that > 'make' only processes the source files that are referenced by the > kernel's .rst files. So if a source file has documentation, but that > source file is not included by one of the .rst files, it won't normally > be processed. > > It is only by running kernel-doc directly against the sources that you > can spot these issues. Ah, thanks for the explanation. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches