From: Jani Nikula <jani.nikula@linux.intel.com>
To: Qianfeng Rong <rongqianfeng@vivo.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>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Qianfeng Rong <rongqianfeng@vivo.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm: Remove redundant __GFP_NOWARN
Date: Thu, 07 Aug 2025 17:13:07 +0300 [thread overview]
Message-ID: <69a17c463c6351b4e0ee03445f59b2d245e85e97@intel.com> (raw)
In-Reply-To: <20250807134639.555274-1-rongqianfeng@vivo.com>
On Thu, 07 Aug 2025, Qianfeng Rong <rongqianfeng@vivo.com> wrote:
> Commit 16f5dfbc851b ("gfp: include __GFP_NOWARN in GFP_NOWAIT")
> made GFP_NOWAIT implicitly include __GFP_NOWARN.
>
> Therefore, explicit __GFP_NOWARN combined with GFP_NOWAIT
> (e.g., `GFP_NOWAIT | __GFP_NOWARN`) is now redundant. Let's clean
> up these redundant flags across subsystems.
>
> No functional changes.
>
> Signed-off-by: Qianfeng Rong <rongqianfeng@vivo.com>
> ---
> drivers/gpu/drm/drm_modeset_lock.c | 4 ++--
Please separate the drm core changes...
> drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c | 4 ++--
> drivers/gpu/drm/i915/i915_active.c | 2 +-
...from the i915 driver changes.
Thanks,
Jani.
> 3 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_modeset_lock.c b/drivers/gpu/drm/drm_modeset_lock.c
> index beb91a13a312..58eac20a8138 100644
> --- a/drivers/gpu/drm/drm_modeset_lock.c
> +++ b/drivers/gpu/drm/drm_modeset_lock.c
> @@ -88,7 +88,7 @@ static noinline depot_stack_handle_t __drm_stack_depot_save(void)
>
> n = stack_trace_save(entries, ARRAY_SIZE(entries), 1);
>
> - return stack_depot_save(entries, n, GFP_NOWAIT | __GFP_NOWARN);
> + return stack_depot_save(entries, n, GFP_NOWAIT);
> }
>
> static void __drm_stack_depot_print(depot_stack_handle_t stack_depot)
> @@ -98,7 +98,7 @@ static void __drm_stack_depot_print(depot_stack_handle_t stack_depot)
> unsigned int nr_entries;
> char *buf;
>
> - buf = kmalloc(PAGE_SIZE, GFP_NOWAIT | __GFP_NOWARN);
> + buf = kmalloc(PAGE_SIZE, GFP_NOWAIT);
> if (!buf)
> return;
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c b/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c
> index 8d4bb95f8424..22432912db2e 100644
> --- a/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c
> +++ b/drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c
> @@ -220,7 +220,7 @@ static void heartbeat(struct work_struct *wrk)
> goto out;
> }
>
> - rq = heartbeat_create(ce, GFP_NOWAIT | __GFP_NOWARN);
> + rq = heartbeat_create(ce, GFP_NOWAIT);
> if (IS_ERR(rq))
> goto unlock;
>
> @@ -282,7 +282,7 @@ static int __intel_engine_pulse(struct intel_engine_cs *engine)
> GEM_BUG_ON(!intel_engine_has_preemption(engine));
> GEM_BUG_ON(!intel_engine_pm_is_awake(engine));
>
> - rq = heartbeat_create(ce, GFP_NOWAIT | __GFP_NOWARN);
> + rq = heartbeat_create(ce, GFP_NOWAIT);
> if (IS_ERR(rq))
> return PTR_ERR(rq);
>
> diff --git a/drivers/gpu/drm/i915/i915_active.c b/drivers/gpu/drm/i915/i915_active.c
> index 0dbc4e289300..402043cd84d5 100644
> --- a/drivers/gpu/drm/i915/i915_active.c
> +++ b/drivers/gpu/drm/i915/i915_active.c
> @@ -727,7 +727,7 @@ int i915_request_await_active(struct i915_request *rq,
> static int sw_await_fence(void *arg, struct dma_fence *fence)
> {
> return i915_sw_fence_await_dma_fence(arg, fence, 0,
> - GFP_NOWAIT | __GFP_NOWARN);
> + GFP_NOWAIT);
> }
>
> int i915_sw_fence_await_active(struct i915_sw_fence *fence,
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-08-07 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 13:46 [PATCH] drm: Remove redundant __GFP_NOWARN Qianfeng Rong
2025-08-07 14:13 ` Jani Nikula [this message]
2025-08-07 14:17 ` Qianfeng Rong
2025-08-07 15:16 ` ✓ i915.CI.BAT: success for " Patchwork
2025-08-07 22:30 ` ✗ i915.CI.Full: failure " Patchwork
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=69a17c463c6351b4e0ee03445f59b2d245e85e97@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=rongqianfeng@vivo.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--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.