Received: by 2002:a05:6500:2018:b0:1fb:9675:f89d with SMTP id t24csp643996lqh; Fri, 31 May 2024 11:43:42 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCWCIGD+xUCQV/4IY+utK4r67pXYnRI/WkcoomcyJ5NZet+zXQ5/XdVVzyTNUP5hE+3Uo8LM2vspCYB3L4c7nIo6VTen+tFgwvZLPxwRLA== X-Google-Smtp-Source: AGHT+IHkzQLtj8Ru3bLwJQaVb9yeCEgXX/JFck88+eKA8tt2bOIdweBnC4XTCNhYc8FhmU6R4igF X-Received: by 2002:a05:620a:a9a:b0:794:ed4f:c64d with SMTP id af79cd13be357-794f5c91440mr285289985a.43.1717181022743; Fri, 31 May 2024 11:43:42 -0700 (PDT) Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [147.75.199.223]) by mx.google.com with ESMTPS id af79cd13be357-794f3064d88si251165385a.345.2024.05.31.11.43.42 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 31 May 2024 11:43:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel+bounces-197312-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=neutral (body hash did not verify) header.i=@intel.com header.s=Intel header.b=CTEsoS62; arc=fail (body hash mismatch); spf=pass (google.com: domain of linux-kernel+bounces-197312-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-kernel+bounces-197312-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com 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 76BA61C23DE7 for ; Fri, 31 May 2024 18:43:42 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id C052E17C223; Fri, 31 May 2024 18:43:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=intel.com header.i=@intel.com header.b="CTEsoS62" Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.18]) (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 4C4667D40D; Fri, 31 May 2024 18:43:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1717181011; cv=none; b=JAMxEuEMvuCZ+t5LOk/haOLepQ0g01nkUo2eXttq/5JzWKSMcljwOaae1eAES/la62pH0pptipMSzDSWWhOiQT8MKdJTmsj8IbeKZ9GB1IgpPPa+NCoDiK3CYh6bPS/93jMuWLld4Nh2BFWOiTSyzWBIXeq4cPlhaQfHxYX+zvM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1717181011; c=relaxed/simple; bh=2998ZpVyEGYSKDxYSM479TmMh5OPYVOX8crtu3Z6n7M=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=rWArWKB8fKAsLQPA+W9HviuSAZFMtgVCTrRt5F1RBcYfSTAWS77NCa0Q4wFcsoyXl7uve2AKIQR/NWVLZ3hlitXg0gj0V55qDhSFkokjx+ggLadHZSpX06Fjq/ZM4JsFNqyAqgGKQUDwQDi3mj8qg06ulIMPi+OiXsJ+hD51xkM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=CTEsoS62; arc=none smtp.client-ip=198.175.65.18 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1717181010; x=1748717010; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=2998ZpVyEGYSKDxYSM479TmMh5OPYVOX8crtu3Z6n7M=; b=CTEsoS624FJb/BCp/Xwn5WHBfwabCbtOzXhn7n/Al6F3128qj9SbhNb2 O7iAWPq9KIWpM9U5x0GeXG3NKMKvdFrjaoJrcy+0YHglRawZPICEUp+RS CML7rzhjFVvcsCEvkMlxiTSxJav/giswcGj3vfLzEIGdqLpAIwsg87lhc xtVtt5/TVIpTT9JApSMzd8FlXyTUaodAZFiD7b81mQ8TFXKPDtpOFJF32 lld6FnM8LyhhTrvqFJviTFPJqa/AABeDRZY91puW704vmBXm2cgm6yqCA c8vVGj8r+LdgpO0WgAJiqXWYvPlCA/sTDrd9ks4W9tdUYfg1QEOJwWmm5 g==; X-CSE-ConnectionGUID: cvU3lHYdRrme9z3CGwZZug== X-CSE-MsgGUID: eFUmf9jcRVydTQ5W77qtig== X-IronPort-AV: E=McAfee;i="6600,9927,11089"; a="13906099" X-IronPort-AV: E=Sophos;i="6.08,205,1712646000"; d="scan'208";a="13906099" Received: from orviesa004.jf.intel.com ([10.64.159.144]) by orvoesa110.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 May 2024 11:43:30 -0700 X-CSE-ConnectionGUID: XalLKdCvTZiIXlO2BFstSA== X-CSE-MsgGUID: x6tLlc2wR5SjtXITRwjjtw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.08,205,1712646000"; d="scan'208";a="41322240" Received: from bergbenj-mobl1.ger.corp.intel.com (HELO localhost) ([10.245.246.190]) by orviesa004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 May 2024 11:43:20 -0700 From: Jani Nikula To: Maxime Ripard , Maarten Lankhorst , Thomas Zimmermann , David Airlie , Daniel Vetter , Jonathan Corbet , Sandy Huang , Heiko =?utf-8?Q?St=C3=BCbner?= , Chen-Yu Tsai , Jernej Skrabec , Samuel Holland , Andy Yan Cc: Hans Verkuil , Sebastian Wick , Ville =?utf-8?B?U3lyasOkbMOk?= , dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, linux-rockchip@lists.infradead.org, linux-sunxi@lists.linux.dev, Maxime Ripard , Dave Stevenson , Sui Jingfeng , Dmitry Baryshkov , Pekka Paalanen , =?utf-8?Q?Ma=C3=ADra?= Canal , Andy Yan Subject: Re: [PATCH v15 00/29] drm/connector: Create HDMI Connector infrastructure In-Reply-To: <20240527-kms-hdmi-connector-state-v15-0-c5af16c3aae2@kernel.org> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20240527-kms-hdmi-connector-state-v15-0-c5af16c3aae2@kernel.org> Date: Fri, 31 May 2024 21:43:16 +0300 Message-ID: <874jadesaj.fsf@intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Mon, 27 May 2024, Maxime Ripard wrote: > Let me know what you think, Sorry to report that this series generates a bunch of kernel-doc warnings in include/drm/drm_connector.h. Documenting nested struct members doesn't work as smoothly as you'd expect: ./include/drm/drm_connector.h:1138: warning: Excess struct member 'broadcast_rgb' description in 'drm_connector_state' ./include/drm/drm_connector.h:1138: warning: Excess struct member 'infoframes' description in 'drm_connector_state' ./include/drm/drm_connector.h:1138: warning: Excess struct member 'avi' description in 'drm_connector_state' ./include/drm/drm_connector.h:1138: warning: Excess struct member 'hdr_drm' description in 'drm_connector_state' ./include/drm/drm_connector.h:1138: warning: Excess struct member 'spd' description in 'drm_connector_state' ./include/drm/drm_connector.h:1138: warning: Excess struct member 'vendor' description in 'drm_connector_state' ./include/drm/drm_connector.h:1138: warning: Excess struct member 'is_limited_range' description in 'drm_connector_state' ./include/drm/drm_connector.h:1138: warning: Excess struct member 'output_bpc' description in 'drm_connector_state' ./include/drm/drm_connector.h:1138: warning: Excess struct member 'output_format' description in 'drm_connector_state' ./include/drm/drm_connector.h:1138: warning: Excess struct member 'tmds_char_rate' description in 'drm_connector_state' ./include/drm/drm_connector.h:2112: warning: Excess struct member 'vendor' description in 'drm_connector' ./include/drm/drm_connector.h:2112: warning: Excess struct member 'product' description in 'drm_connector' ./include/drm/drm_connector.h:2112: warning: Excess struct member 'supported_formats' description in 'drm_connector' ./include/drm/drm_connector.h:2112: warning: Excess struct member 'infoframes' description in 'drm_connector' ./include/drm/drm_connector.h:2112: warning: Excess struct member 'lock' description in 'drm_connector' ./include/drm/drm_connector.h:2112: warning: Excess struct member 'audio' description in 'drm_connector' Noticed this when I was rebasing [1]. Having that merged would find issues in headers at build time instead of 'make htmldocs'. In the mean time, this is the quick reproducer: $ scripts/kernel-doc -none include/drm/drm_connector.h BR, Jani. [1] https://lore.kernel.org/r/20240402140136.1722533-1-jani.nikula@intel.com -- Jani Nikula, Intel