lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 15 Jul 2022 17:32:57 -0400 From: Rodrigo Vivi <rodrigo.vivi@...el.com> To: Mauro Carvalho Chehab <mchehab@...nel.org> CC: Tvrtko Ursulin <tvrtko.ursulin@...ux.intel.com>, David Airlie <airlied@...ux.ie>, <intel-gfx@...ts.freedesktop.org>, <linux-kernel@...r.kernel.org>, <dri-devel@...ts.freedesktop.org> Subject: Re: [PATCH v2 25/39] drm/i915: i915_vma_resource.c: fix some kernel-doc markups On Wed, Jul 13, 2022 at 09:12:13AM +0100, Mauro Carvalho Chehab wrote: > Building docs currently produces two warnings: > > Documentation/foo/i915:71: ./drivers/gpu/drm/i915/i915_vma_resource.c:286: WARNING: Inline strong start-string without end-string. > Documentation/foo/i915:71: ./drivers/gpu/drm/i915/i915_vma_resource.c:370: WARNING: Inline strong start-string without end-string. > > That's because @foo evaluates into **foo**, and placing anything > after it without spaces cause Sphinx to warn and do the wrong > thing.. So, replace them by a different Sphinx-compatible tag. > > Signed-off-by: Mauro Carvalho Chehab <mchehab@...nel.org> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@...el.com> > --- > > To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. > See [PATCH v2 00/39] at: https://lore.kernel.org/all/cover.1657699522.git.mchehab@kernel.org/ > > drivers/gpu/drm/i915/i915_vma_resource.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/i915/i915_vma_resource.c b/drivers/gpu/drm/i915/i915_vma_resource.c > index 27c55027387a..fa5a678018d9 100644 > --- a/drivers/gpu/drm/i915/i915_vma_resource.c > +++ b/drivers/gpu/drm/i915/i915_vma_resource.c > @@ -283,7 +283,7 @@ i915_vma_resource_color_adjust_range(struct i915_address_space *vm, > * > * The function needs to be called with the vm lock held. > * > - * Return: Zero on success, -ERESTARTSYS if interrupted and @intr==true > + * Return: Zero on success, -ERESTARTSYS if interrupted and ``intr==true`` > */ > int i915_vma_resource_bind_dep_sync(struct i915_address_space *vm, > u64 offset, > @@ -367,7 +367,7 @@ void i915_vma_resource_bind_dep_sync_all(struct i915_address_space *vm) > * this means that during heavy memory pressure, we will sync in this > * function. > * > - * Return: Zero on success, -ERESTARTSYS if interrupted and @intr==true > + * Return: Zero on success, -ERESTARTSYS if interrupted and ``intr==true`` > */ > int i915_vma_resource_bind_dep_await(struct i915_address_space *vm, > struct i915_sw_fence *sw_fence, > -- > 2.36.1 >
Powered by blists - more mailing lists