From: Matthew Brost <matthew.brost@intel.com>
To: Min-Hua Chen <minhuadotchen@gmail.com>
Cc: "Christian Koenig" <christian.koenig@amd.com>,
"Huang Rui" <ray.huang@amd.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-next] drm/ttm: make ttm_swap_ops static
Date: Sat, 7 Sep 2024 17:34:48 +0000 [thread overview]
Message-ID: <ZtyOuDQtWHU4Phr7@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240907033643.1513301-1-minhuadotchen@gmail.com>
On Sat, Sep 07, 2024 at 11:36:41AM +0800, Min-Hua Chen wrote:
> make ttm_swap_ops static to fix the following sparse warning:
>
> drivers/gpu/drm/ttm/ttm_bo.c:1142:31: sparse: warning: symbol
> 'ttm_swap_ops' was not declared. Should it be static?
>
This looks correct. I'd drop the 'Should it be static?' from commit
messge though. Assume a maintainer of TTM can drop at megre time.
With that:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> Fixes: 10efe34dae79 ("drm/ttm: Use the LRU walker helper for swapping")
> Signed-off-by: Min-Hua Chen <minhuadotchen@gmail.com>
> ---
> drivers/gpu/drm/ttm/ttm_bo.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
> index 320592435252..1aab30767e41 100644
> --- a/drivers/gpu/drm/ttm/ttm_bo.c
> +++ b/drivers/gpu/drm/ttm/ttm_bo.c
> @@ -1139,7 +1139,7 @@ ttm_bo_swapout_cb(struct ttm_lru_walk *walk, struct ttm_buffer_object *bo)
> return ret;
> }
>
> -const struct ttm_lru_walk_ops ttm_swap_ops = {
> +static const struct ttm_lru_walk_ops ttm_swap_ops = {
> .process_bo = ttm_bo_swapout_cb,
> };
>
> --
> 2.43.0
>
prev parent reply other threads:[~2024-09-07 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 3:36 Min-Hua Chen
2024-09-07 17:34 ` Matthew Brost [this message]
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=ZtyOuDQtWHU4Phr7@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=minhuadotchen@gmail.com \
--cc=mripard@kernel.org \
--cc=ray.huang@amd.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®