Received: by 2002:a05:7412:8521:b0:e2:908c:2ebd with SMTP id t33csp2359580rdf; Mon, 6 Nov 2023 11:41:58 -0800 (PST) X-Google-Smtp-Source: AGHT+IHHEJtJ4ghpkjmynqKRNu1KRxaxW5lZ80j1ZttjO9EWw0r14cQbWiRc/6EBB9rw43x1d/zI X-Received: by 2002:a17:902:d28b:b0:1cc:13d0:d515 with SMTP id t11-20020a170902d28b00b001cc13d0d515mr20716689plc.20.1699299718167; Mon, 06 Nov 2023 11:41:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1699299718; cv=none; d=google.com; s=arc-20160816; b=pWFS1HTC3Ax/ZrHM2jhZ+eh1I7zLwmZTqKi0t1FFwjjiBDXW5vpl1WTMv1+CRBiE5Z BHMY6Biym2FYj/Zb8vfGwVtgcRx1TN9sbUFG5AoduEVy0vetYsTo8HqT91NmO1IEMm2P MxotyPLnvuWzj3iZHtctKHBcf5wnk6z7XJixq59pMB4Z1O+hCypYTOnBNqJ5Nh1TSQno JExkigTssllfBTXNVh1wbq7GhxeBjBEKkkG24e4XcCtnRFszZeHNFKf395lik4OJKpDj OTIflsL3Fdsjh5RRj0tXwaHOaowDXveAdiuj5u1oWPP7I9H8p/Phx6cGP+/ROY3xtTx4 iVZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:references:organization:in-reply-to:subject:cc:to :from:dkim-signature; bh=Y/iOyvCyBrm2F7uqJMlk/AWrWhCdasZYJRHUflbv8Zk=; fh=iIP9bFGvLjI/pg5LV+cl6TyWhjoP822DDLTuEN4EjTE=; b=pFCVzlsNnvg60fgISMNBjca2M3X8NNNx+uRaeNqTJPgRUw+v0kMt6/YzRjzB8wSGVb tUBghF/cEqL5E+EU+LmlkVKydKICYenS17FETbipZMGuJo0oUG4+9FtjkW3RsGqrjnJA aL484ttjIHwW+v5Qtpf4IQ3K0QutT1kTyKzasLjlStwlh4Kg/aY91fpXEGiHQH94pisW seN0qz5pCEZ92sxR8VjwKM39VdUp+jDmApEE+v4ZmhV/04vuWCEpNDv4fVZDUSM5qjWA wQxx2toswD4FZe7QlY8Jp9v4OxQUykqdh6UVqcU7h6cbXyBqCdQ8xVsb0nHv0gP00cXM W7Dw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=iQSbzzqE; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from fry.vger.email (fry.vger.email. [23.128.96.38]) by mx.google.com with ESMTPS id c9-20020a170902d48900b001cc1eab0fe4si9259486plg.298.2023.11.06.11.41.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 06 Nov 2023 11:41:58 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=iQSbzzqE; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by fry.vger.email (Postfix) with ESMTP id 4170780C3444; Mon, 6 Nov 2023 11:41:55 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at fry.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232508AbjKFTlg (ORCPT + 99 others); Mon, 6 Nov 2023 14:41:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58632 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231773AbjKFTlf (ORCPT ); Mon, 6 Nov 2023 14:41:35 -0500 Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3690F98; Mon, 6 Nov 2023 11:41:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1699299692; x=1730835692; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version:content-transfer-encoding; bh=/ApfnDGctoPRAAUz0Kk3TUlchg/jcOFSHz85tJuZkgQ=; b=iQSbzzqExDIWIJ+5moHdjFlXNT2PSeWgndQxNYMjMiH5utSwZPnOgdCe 1obNPwOkUl0J4q4Dgf/q9FoEOne6lp/ahToz7xY43CTcBk1erUXp0Be+a /sTklisw+sCb1LkwDLKntfxTrRbb6/h7ErPy/hQUqzLpjm6RgWTFQL9yB bIgAgFKEXafgHdNWW6ef5CeJkMlcO2l+vvUUWX1AC5lzrE6VFdoB3qfiJ Y91O09XCfmORNb66cwUAGUk5Pj//Kej7y24bXLDxijXJWKrkBriJiPgyL Qk+K91rUItVHYRiwG077LxmILxgLbaLTvBW5b0lOqfsFYjIdMyuQ3WpXE g==; X-IronPort-AV: E=McAfee;i="6600,9927,10886"; a="393246961" X-IronPort-AV: E=Sophos;i="6.03,282,1694761200"; d="scan'208";a="393246961" Received: from orviesa002.jf.intel.com ([10.64.159.142]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Nov 2023 11:41:31 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.03,282,1694761200"; d="scan'208";a="3556452" Received: from lpilolli-mobl.ger.corp.intel.com (HELO localhost) ([10.252.36.222]) by orviesa002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Nov 2023 11:41:29 -0800 From: Jani Nikula To: Hunter Chasens Cc: Bagas Sanjaya , corbet@lwn.net, Luca Coelho , airlied@gmail.com, daniel@ffwll.ch, maarten.lankhorst@linux.intel.com, mripard@kernel.org, tzimmermann@suse.de, dri-devel@lists.freedesktop.org, Linux Documentation , Linux Kernel Mailing List Subject: Re: [PATCH v1] docs: gpu: rfc: i915_scheduler.rst remove unused directives for namespacing In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20231104134708.69432-1-hunter.chasens18@ncf.edu> <8734xj18ck.fsf@intel.com> Date: Mon, 06 Nov 2023 21:41:25 +0200 Message-ID: <87edh2zn2y.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on fry.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (fry.vger.email [0.0.0.0]); Mon, 06 Nov 2023 11:41:55 -0800 (PST) On Mon, 06 Nov 2023, Hunter Chasens wrote: > When running `make htmldocs` the following warnings are given. > > ``` > Documentation/gpu/rfc/i915_scheduler.rst:138: WARNING: > Unknown directive type "c:namespace-push". > > .. c:namespace-push:: rfc > Documentation/gpu/rfc/i915_scheduler.rst:143: WARNING: > Unknown directive type "c:namespace-pop". > > .. c:namespace-pop:: > ``` > > The kernel test robot also reported it here. > Link: https://lore.kernel.org/all/202311061623.86pTQrie-lkp@intel.com/ > > Last year Maryam Tahhan from Redhat noticed something > similar. "The missing support of c:namespace-push:: and c:namespace-pop:: > directives by helper scripts for kernel documentation prevents using the > ``c:function::`` directive with proper namespacing." From the context, it > sounds like this was brought about from a Sphinx update. > > Link: https://lore.kernel.org/all/20221123092321.88558-3-mtahhan@redhat.c= om/ > > When compiled the `.. kernel-doc::` literal gives it the same formatting = with > or without the namespace directives present. Due to the above information= I > think it safe to remove these, as they don't seem to do anything but > throw warnings. Not so fast! Looks like this is because namespacing was introduced in Sphinx 3.1 [1]. With earlier Sphinx, you get a warning about the namespace directives. However, with newer Sphinx, you get the warning mentioned in commit f6757dfcfde7 ("drm/doc: fix duplicate declaration warning") if you remove the namespace directives: linux/Documentation/gpu/driver-uapi.rst:2279: WARNING: Duplicate C declarat= ion, also defined at rfc/i915_scheduler:3. Declaration is '.. c:struct:: i915_context_engines_parallel_submit'. It would be short-sighted to just remove the directives. Sooner or later we're gong to bump the (IMO extremely conservative) minimum version requirement. BR, Jani. [1] https://www.sphinx-doc.org/en/master/usage/domains/c.html#namespacing > > On Mon, Nov 6, 2023 at 5:31=E2=80=AFAM Jani Nikula wrote: >> >> On Mon, 06 Nov 2023, Bagas Sanjaya wrote: >> > On Sat, Nov 04, 2023 at 09:47:08AM -0400, Hunter Chasens wrote: >> >> diff --git a/Documentation/gpu/rfc/i915_scheduler.rst b/Documentation= /gpu/rfc/i915_scheduler.rst >> >> index c237ebc024cd..23ba7006929b 100644 >> >> --- a/Documentation/gpu/rfc/i915_scheduler.rst >> >> +++ b/Documentation/gpu/rfc/i915_scheduler.rst >> >> @@ -135,13 +135,9 @@ Add I915_CONTEXT_ENGINES_EXT_PARALLEL_SUBMIT and >> >> drm_i915_context_engines_parallel_submit to the uAPI to implement th= is >> >> extension. >> >> >> >> -.. c:namespace-push:: rfc >> >> - >> >> .. kernel-doc:: include/uapi/drm/i915_drm.h >> >> :functions: i915_context_engines_parallel_submit >> >> >> >> -.. c:namespace-pop:: >> >> - >> >> What makes the namespacing unnecessary? >> >> $ git grep '.. kernel-doc:: include/uapi/drm/i915_drm.h' >> Documentation/gpu/driver-uapi.rst:.. kernel-doc:: include/uapi/drm/i915_= drm.h >> Documentation/gpu/rfc/i915_scheduler.rst:.. kernel-doc:: include/uapi/dr= m/i915_drm.h >> >> And you get [1] and [2]. >> >> >> Extend execbuf2 IOCTL to support submitting N BBs in a single IOCTL >> >> ------------------------------------------------------------------- >> >> Contexts that have been configured with the 'set_parallel' extension= can only >> > >> > The warnings go away, thanks! >> >> What warnings go away? >> >> BR, >> Jani. >> >> >> [1] https://docs.kernel.org/gpu/driver-uapi.html#c.i915_context_engines_= parallel_submit >> [2] https://docs.kernel.org/gpu/rfc/i915_scheduler.html#c.rfc.i915_conte= xt_engines_parallel_submit >> >> > >> > Fixes: f6757dfcfde7 ("drm/doc: fix duplicate declaration warning") >> > Reviewed-by: Bagas Sanjaya >> >> -- >> Jani Nikula, Intel --=20 Jani Nikula, Intel