From: Boris Brezillon <boris.brezillon@collabora.com>
To: Liviu Dudau <liviu.dudau@arm.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Steven Price <steven.price@arm.com>
Subject: Re: [PATCH 2/2] drm/panthor: Fix some kerneldoc warnings
Date: Wed, 3 Apr 2024 08:46:32 +0200 [thread overview]
Message-ID: <20240403084632.1d00d1c6@collabora.com> (raw)
In-Reply-To: <20240402215423.360341-2-liviu.dudau@arm.com>
On Tue, 2 Apr 2024 22:54:23 +0100
Liviu Dudau <liviu.dudau@arm.com> wrote:
> When compiling with W=1 the build process will flag empty comments,
> misnamed documented variables and incorrect tagging of functions.
> Fix them in one go.
>
> Fixes: de8548813824 ("drm/panthor: Add the scheduler logical block")
> Cc: Boris Brezillon <boris.brezillon@collabora.com>
> Cc: Steven Price <steven.price@arm.com>
> Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
> ---
> drivers/gpu/drm/panthor/panthor_sched.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_sched.c b/drivers/gpu/drm/panthor/panthor_sched.c
> index e5a710f190d2a8..a787f2fea33e98 100644
> --- a/drivers/gpu/drm/panthor/panthor_sched.c
> +++ b/drivers/gpu/drm/panthor/panthor_sched.c
> @@ -517,7 +517,7 @@ struct panthor_group {
> /** @max_compute_cores: Maximum number of shader cores used for compute jobs. */
> u8 max_compute_cores;
>
> - /** @max_compute_cores: Maximum number of shader cores used for fragment jobs. */
> + /** @max_fragment_cores: Maximum number of shader cores used for fragment jobs. */
> u8 max_fragment_cores;
>
> /** @max_tiler_cores: Maximum number of tiler cores used for tiler jobs. */
> @@ -993,7 +993,7 @@ cs_slot_prog_locked(struct panthor_device *ptdev, u32 csg_id, u32 cs_id)
> }
>
> /**
> - * @cs_slot_reset_locked() - Reset a queue slot
> + * cs_slot_reset_locked() - Reset a queue slot
> * @ptdev: Device.
> * @csg_id: Group slot.
> * @cs_id: Queue slot.
> @@ -1591,7 +1591,7 @@ static void sched_process_idle_event_locked(struct panthor_device *ptdev)
> }
>
> /**
> - * panthor_sched_process_global_irq() - Process the scheduling part of a global IRQ
> + * sched_process_global_irq_locked() - Process the scheduling part of a global IRQ
> * @ptdev: Device.
> */
> static void sched_process_global_irq_locked(struct panthor_device *ptdev)
> @@ -1660,8 +1660,6 @@ static const struct dma_fence_ops panthor_queue_fence_ops = {
> .get_timeline_name = queue_fence_get_timeline_name,
> };
>
> -/**
> - */
> struct panthor_csg_slots_upd_ctx {
> u32 update_mask;
> u32 timedout_mask;
next prev parent reply other threads:[~2024-04-03 6:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 21:54 [PATCH 1/2] drm/panthor: Cleanup unused variable 'cookie' Liviu Dudau
2024-04-02 21:54 ` [PATCH 2/2] drm/panthor: Fix some kerneldoc warnings Liviu Dudau
2024-04-03 6:46 ` Boris Brezillon [this message]
2024-04-03 6:46 ` [PATCH 1/2] drm/panthor: Cleanup unused variable 'cookie' Boris Brezillon
2024-04-03 7:15 ` Boris Brezillon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240403084632.1d00d1c6@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=steven.price@arm.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.