Message ID | 20240126-gix-mtk-warnings-v1-17-eed7865fce18@chromium.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel+bounces-40835-ouuuleilei=gmail.com@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a05:7301:2395:b0:106:343:edcb with SMTP id gw21csp211337dyb; Fri, 26 Jan 2024 15:32:11 -0800 (PST) X-Google-Smtp-Source: AGHT+IGLfZgNOXpCkWjdJpf5Ih4/f6EhsjluVRzhxH0EGN++gjxJ4TRFYdfxcgWNh3zlwQYbwnN7 X-Received: by 2002:a1c:4c0c:0:b0:40e:d1ba:1cf7 with SMTP id z12-20020a1c4c0c000000b0040ed1ba1cf7mr409318wmf.129.1706311930938; Fri, 26 Jan 2024 15:32:10 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1706311930; cv=pass; d=google.com; s=arc-20160816; b=Q/98QVSDlJID02iq+DLckGdHaBlLBN0D5I6xfzwwDPbfMo7hOSqMsB8eTS/bPalXkk IXUyp5GOm+AiGiPHN3HjplhTPlSGnZm9rmsUxTvq/l/XzFXJxmPxgpZGrncmmE+7Z4rh lSU83KbZctawHevAayeZ1Y/oo5LewwcsFQt+mk0wbYTtrt8ylVpHHKzVYrItH9Mq3a2Y oNxksPR7BfK8oOiILARuB8/cc98CMbX/VujGsZPNkD+rEkfTnpwWwn2TrOZmooF0uk1q 7L9EC3GR+ia/qAk55OFjToGHurXySmL21ESRJDZgxGUMckpibNL927XtWXd26vAjrS/n vLDA== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=cc:to:in-reply-to:references:message-id:content-transfer-encoding :mime-version:list-unsubscribe:list-subscribe:list-id:precedence :subject:date:from:dkim-signature; bh=mtltgslBdQHae+oLD1399tQsPexikCLm+b/oIxSwL94=; fh=OSrJNbj+8S6AzSmIaZjMzeOT7crYO3DQlxVMz8SQo/I=; b=pbeVSxr1v6D9lYGl36R8PwIxpwx3PGHL/Y2E/442I9eAJPAHAGRv4yfjmMwtMxuX+N OX4TtI74b4icHJaCbbF7bU3oqCG2P8tGMWVPd/ofhktWNWUhqVik0rw8eZygYLKJc9jj rnsTuFTKv+aGK+TNGwa95FyG4kdtEFJe4OHdJBqSOmDSIoyQRWlTeopVRmlCREUXqBjg 1bcrL8DL0gjcSLkTEBjCjlIenoH9enQO61d0c8pVdtqEAt44QRfxtHYIyO4XDngujFjP +B/x08ndTamJ+16ris3rk4XD9W9hqAO0/zNxK9jfpxxkuL+m6ZXJw3GVUy+lxVv20yBl Pixg== ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=l6pzT6fi; arc=pass (i=1 spf=pass spfdomain=chromium.org dkim=pass dkdomain=chromium.org dmarc=pass fromdomain=chromium.org); spf=pass (google.com: domain of linux-kernel+bounces-40835-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-40835-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [2604:1380:4601:e00::3]) by mx.google.com with ESMTPS id f15-20020a17090624cf00b00a35200615d5si379058ejb.763.2024.01.26.15.32.10 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Jan 2024 15:32:10 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-40835-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=l6pzT6fi; arc=pass (i=1 spf=pass spfdomain=chromium.org dkim=pass dkdomain=chromium.org dmarc=pass fromdomain=chromium.org); spf=pass (google.com: domain of linux-kernel+bounces-40835-ouuuleilei=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-40835-ouuuleilei=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org 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 am.mirrors.kernel.org (Postfix) with ESMTPS id 407151F2A052 for <ouuuleilei@gmail.com>; Fri, 26 Jan 2024 23:23:22 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 5A497657A3; Fri, 26 Jan 2024 23:16:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="l6pzT6fi" Received: from mail-qk1-f178.google.com (mail-qk1-f178.google.com [209.85.222.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CE9D8627E4 for <linux-kernel@vger.kernel.org>; Fri, 26 Jan 2024 23:16:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.222.178 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706310986; cv=none; b=Z5jPxEc3SCAu0NSJhAMXuizxvs1n345dcpdA4T4ndINCnpGwGPuT4N8ns0E/jAIiN8oEDbyUU/OEfpNQ39wuXS8AzRAw0gyXgCqHGqMWjaPsbf6a2G8RiatcgxOTssSuuJEA3k30DX97WlfmVFo9fOoRXCRnwpFKAtFvSe/gqe4= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706310986; c=relaxed/simple; bh=3a/r7kXdAIFtktUyOV8TMLOQckxM8aU1T8MlUOBhuxg=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:References: In-Reply-To:To:Cc; b=hlYF886X2ccwQTN5DnwqsCMZvmvWlJwRW6Scr0VY7Qx8PJPpM/VMmt/o19J2x3+A2yBuTIL8JqXtlHpgcPptD3Pod7nppgYspndJdK9YvnpY9G4UB5QRd1zG2SHutOE5iVKGXL9vva2oX9OEmS57m/9GWU3ei25/Wkrxif+AD0U= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org; spf=pass smtp.mailfrom=chromium.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b=l6pzT6fi; arc=none smtp.client-ip=209.85.222.178 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=chromium.org Received: by mail-qk1-f178.google.com with SMTP id af79cd13be357-783d4b3ad96so78746785a.3 for <linux-kernel@vger.kernel.org>; Fri, 26 Jan 2024 15:16:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1706310983; x=1706915783; darn=vger.kernel.org; h=cc:to:in-reply-to:references:message-id:content-transfer-encoding :mime-version:subject:date:from:from:to:cc:subject:date:message-id :reply-to; bh=mtltgslBdQHae+oLD1399tQsPexikCLm+b/oIxSwL94=; b=l6pzT6fiQre9odpIZATrtgsshg4nH0dv4jI7iWbvVve7/y8ej97RVaZAbruMZD0pSu B1WrPPkVG8OazVZ5fOMdinRIfskfwkL+35PAKDYHJHka/PQkwiggwB2lp7erSeiw49zn Ugr+lr9r2rK/FoUdl8b2zxcprozmtlRXpE930= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706310983; x=1706915783; h=cc:to:in-reply-to:references:message-id:content-transfer-encoding :mime-version:subject:date:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=mtltgslBdQHae+oLD1399tQsPexikCLm+b/oIxSwL94=; b=BCjmbLDQgDrmULb9gm7uZTGMkDrOTXHGInif6YFM9X01uNQhpP08fj3dU+gFQ/gsTu R7O8m2qy26IdVp6uJjL6ED6B88AW8lCRniEY8e3KoinntnPany3ujxDRF8hp/m1kJext xGUKHCMvm3T7OMi422xhg3bQfSrgZbFkL4R21favxRVzk6t+vSIDTmSCJ5oRPXiuMsyj di7VcCg/SY6dM9TBy4aCwc3ghlFxN2yTeCYv4sW9P2IysfUmiIguCL8wHjQtq0gzJIuI q4/o9vFe7kdNj/jmxJtx9fSvq3jKPwDKy298nP4VRx9bP/FAo8Cpbsd0l86/0OkaGzZM sc0w== X-Gm-Message-State: AOJu0Yy0xtSISz1j4ZqMPzx1Te9WRjGy8RJLRAR7UA3sKXVgxRbUI4Ow QLtYdbVI5PP/c5hSg+jxKj7Ro79OEk65JdqdeODQECrPQSuchlkq6/4szn9C7A== X-Received: by 2002:a05:620a:618e:b0:783:4cbd:9ed7 with SMTP id or14-20020a05620a618e00b007834cbd9ed7mr711408qkn.38.1706310983521; Fri, 26 Jan 2024 15:16:23 -0800 (PST) Received: from denia.c.googlers.com (240.157.150.34.bc.googleusercontent.com. [34.150.157.240]) by smtp.gmail.com with ESMTPSA id m4-20020a05620a290400b00783de3ddf5esm507358qkp.70.2024.01.26.15.16.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 26 Jan 2024 15:16:23 -0800 (PST) From: Ricardo Ribalda <ribalda@chromium.org> Date: Fri, 26 Jan 2024 23:16:16 +0000 Subject: [PATCH 17/17] linux: v4l2-vp9.h: Fix kerneldoc Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: <linux-kernel.vger.kernel.org> List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org> List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <20240126-gix-mtk-warnings-v1-17-eed7865fce18@chromium.org> References: <20240126-gix-mtk-warnings-v1-0-eed7865fce18@chromium.org> In-Reply-To: <20240126-gix-mtk-warnings-v1-0-eed7865fce18@chromium.org> To: Tiffany Lin <tiffany.lin@mediatek.com>, Andrew-CT Chen <andrew-ct.chen@mediatek.com>, Yunfei Dong <yunfei.dong@mediatek.com>, Mauro Carvalho Chehab <mchehab@kernel.org>, Matthias Brugger <matthias.bgg@gmail.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, Sakari Ailus <sakari.ailus@linux.intel.com>, Laurent Pinchart <laurent.pinchart@ideasonboard.com>, Hans Verkuil <hverkuil-cisco@xs4all.nl>, Hans Verkuil <hverkuil@xs4all.nl>, Kieran Bingham <kieran.bingham@ideasonboard.com>, Bin Liu <bin.liu@mediatek.com>, Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>, Philipp Zabel <p.zabel@pengutronix.de>, Stanimir Varbanov <stanimir.k.varbanov@gmail.com>, Vikash Garodia <quic_vgarodia@quicinc.com>, Bryan O'Donoghue <bryan.odonoghue@linaro.org>, Bjorn Andersson <andersson@kernel.org>, Konrad Dybcio <konrad.dybcio@linaro.org>, Sylwester Nawrocki <s.nawrocki@samsung.com>, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, Alim Akhtar <alim.akhtar@samsung.com>, Marek Szyprowski <m.szyprowski@samsung.com>, Andrzej Hajda <andrzej.hajda@intel.com>, Bingbu Cao <bingbu.cao@intel.com>, Tianshu Qiu <tian.shu.qiu@intel.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Neil Armstrong <neil.armstrong@linaro.org>, Kevin Hilman <khilman@baylibre.com>, Jerome Brunet <jbrunet@baylibre.com>, Martin Blumenstingl <martin.blumenstingl@googlemail.com> Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-staging@lists.linux.dev, linux-amlogic@lists.infradead.org, Ricardo Ribalda <ribalda@chromium.org> X-Mailer: b4 0.12.3 X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1789197739332770220 X-GMAIL-MSGID: 1789197739332770220 |
Series |
media: kerneldoc warnings
|
|
Commit Message
Ricardo Ribalda
Jan. 26, 2024, 11:16 p.m. UTC
Kerneldoc cannot understand arrays defined like
v4l2_frame_symbol_counts.
Adding an asterisk to the name does do the trick.
Disable the kerneldoc notation for now, it is already ignored:
https://docs.kernel.org/search.html?q=v4l2_vp9_frame_symbol_counts
include/media/v4l2-vp9.h:144: warning: Excess struct member 'partition' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'skip' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'intra_inter' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'tx32p' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'tx16p' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'tx8p' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'y_mode' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'uv_mode' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'comp' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'comp_ref' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'single_ref' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'mv_mode' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'filter' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'mv_joint' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'sign' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'classes' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'class0' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'bits' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'class0_fp' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'fp' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'class0_hp' description in 'v4l2_vp9_frame_symbol_counts'
include/media/v4l2-vp9.h:144: warning: Excess struct member 'hp' description in 'v4l2_vp9_frame_symbol_counts'
Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
---
include/media/v4l2-vp9.h | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
Comments
Hi Ricardo, On Fri, Jan 26, 2024 at 11:16:16PM +0000, Ricardo Ribalda wrote: > Kerneldoc cannot understand arrays defined like > v4l2_frame_symbol_counts. > > Adding an asterisk to the name does do the trick. > > Disable the kerneldoc notation for now, it is already ignored: > https://docs.kernel.org/search.html?q=v4l2_vp9_frame_symbol_counts Wouldn't it be nicer to fix kerneldoc instead? It might not be difficult at all. Feel free to, but I can also give it a try.
On 27/01/2024 10:57, Sakari Ailus wrote: > Hi Ricardo, > > On Fri, Jan 26, 2024 at 11:16:16PM +0000, Ricardo Ribalda wrote: >> Kerneldoc cannot understand arrays defined like >> v4l2_frame_symbol_counts. >> >> Adding an asterisk to the name does do the trick. >> >> Disable the kerneldoc notation for now, it is already ignored: >> https://docs.kernel.org/search.html?q=v4l2_vp9_frame_symbol_counts > > Wouldn't it be nicer to fix kerneldoc instead? It might not be difficult at > all. > > Feel free to, but I can also give it a try. > It would be nice to have this fixed in kerneldoc itself. I'm holding this patch back for two weeks to see if someone wants to work on kerneldoc. If not, then I'll take this anyway to fix the noise in our build. Note that while this header is indeed ignored in the documentation, that is really more a bug and it would be nice to actually include this header somewhere in our documentation. So fixing these kerneldoc warnings one way or another is something that we should do. Regards, Hans
On 2/5/24 02:29, Hans Verkuil wrote: > On 27/01/2024 10:57, Sakari Ailus wrote: >> Hi Ricardo, >> >> On Fri, Jan 26, 2024 at 11:16:16PM +0000, Ricardo Ribalda wrote: >>> Kerneldoc cannot understand arrays defined like >>> v4l2_frame_symbol_counts. >>> >>> Adding an asterisk to the name does do the trick. >>> >>> Disable the kerneldoc notation for now, it is already ignored: >>> https://docs.kernel.org/search.html?q=v4l2_vp9_frame_symbol_counts >> >> Wouldn't it be nicer to fix kerneldoc instead? It might not be difficult at >> all. >> >> Feel free to, but I can also give it a try. >> > > It would be nice to have this fixed in kerneldoc itself. I'm holding this > patch back for two weeks to see if someone wants to work on kerneldoc. > > If not, then I'll take this anyway to fix the noise in our build. > > Note that while this header is indeed ignored in the documentation, that > is really more a bug and it would be nice to actually include this header > somewhere in our documentation. So fixing these kerneldoc warnings one way > or another is something that we should do. > It's just waiting for Jon to apply it: (from Sakari) https://lore.kernel.org/all/20240131084934.191226-1-sakari.ailus@linux.intel.com/ Thanks.
On 05/02/2024 11:39, Randy Dunlap wrote: > > > On 2/5/24 02:29, Hans Verkuil wrote: >> On 27/01/2024 10:57, Sakari Ailus wrote: >>> Hi Ricardo, >>> >>> On Fri, Jan 26, 2024 at 11:16:16PM +0000, Ricardo Ribalda wrote: >>>> Kerneldoc cannot understand arrays defined like >>>> v4l2_frame_symbol_counts. >>>> >>>> Adding an asterisk to the name does do the trick. >>>> >>>> Disable the kerneldoc notation for now, it is already ignored: >>>> https://docs.kernel.org/search.html?q=v4l2_vp9_frame_symbol_counts >>> >>> Wouldn't it be nicer to fix kerneldoc instead? It might not be difficult at >>> all. >>> >>> Feel free to, but I can also give it a try. >>> >> >> It would be nice to have this fixed in kerneldoc itself. I'm holding this >> patch back for two weeks to see if someone wants to work on kerneldoc. >> >> If not, then I'll take this anyway to fix the noise in our build. >> >> Note that while this header is indeed ignored in the documentation, that >> is really more a bug and it would be nice to actually include this header >> somewhere in our documentation. So fixing these kerneldoc warnings one way >> or another is something that we should do. >> > > It's just waiting for Jon to apply it: (from Sakari) > > https://lore.kernel.org/all/20240131084934.191226-1-sakari.ailus@linux.intel.com/ Ah, that patch was CCed to me but not to linux-media, and I only searched linux-media for it so I missed it. Good news that this is fixed in the right place. I marked this 17/17 patch as Obsoleted in patchwork. Regards, Hans
Hi Hans, On Mon, Feb 05, 2024 at 11:44:13AM +0100, Hans Verkuil wrote: > On 05/02/2024 11:39, Randy Dunlap wrote: > > > > > > On 2/5/24 02:29, Hans Verkuil wrote: > >> On 27/01/2024 10:57, Sakari Ailus wrote: > >>> Hi Ricardo, > >>> > >>> On Fri, Jan 26, 2024 at 11:16:16PM +0000, Ricardo Ribalda wrote: > >>>> Kerneldoc cannot understand arrays defined like > >>>> v4l2_frame_symbol_counts. > >>>> > >>>> Adding an asterisk to the name does do the trick. > >>>> > >>>> Disable the kerneldoc notation for now, it is already ignored: > >>>> https://docs.kernel.org/search.html?q=v4l2_vp9_frame_symbol_counts > >>> > >>> Wouldn't it be nicer to fix kerneldoc instead? It might not be difficult at > >>> all. > >>> > >>> Feel free to, but I can also give it a try. > >>> > >> > >> It would be nice to have this fixed in kerneldoc itself. I'm holding this > >> patch back for two weeks to see if someone wants to work on kerneldoc. > >> > >> If not, then I'll take this anyway to fix the noise in our build. > >> > >> Note that while this header is indeed ignored in the documentation, that > >> is really more a bug and it would be nice to actually include this header > >> somewhere in our documentation. So fixing these kerneldoc warnings one way > >> or another is something that we should do. > >> > > > > It's just waiting for Jon to apply it: (from Sakari) > > > > https://lore.kernel.org/all/20240131084934.191226-1-sakari.ailus@linux.intel.com/ > > Ah, that patch was CCed to me but not to linux-media, and I only searched linux-media > for it so I missed it. Good news that this is fixed in the right place. My bad, somehow I missed linux-media from the distribution. :-( > > I marked this 17/17 patch as Obsoleted in patchwork. Thank you!
diff --git a/include/media/v4l2-vp9.h b/include/media/v4l2-vp9.h index 05478ad6d4ab..f0d80273bd61 100644 --- a/include/media/v4l2-vp9.h +++ b/include/media/v4l2-vp9.h @@ -83,7 +83,11 @@ struct v4l2_vp9_frame_context { struct v4l2_vp9_frame_mv_context mv; }; -/** +/* + * NOTE: This is not a kerneldoc, because the (*name) notation confuses the + * parser. + */ +/* * struct v4l2_vp9_frame_symbol_counts - pointers to arrays of symbol counts * * @partition: partition counts.