From: Jani Nikula <jani.nikula@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH v1 0/2] drm/i915/fence: A couple of build fixes
Date: Thu, 29 Aug 2024 19:38:08 +0300 [thread overview]
Message-ID: <87cylrwahb.fsf@intel.com> (raw)
In-Reply-To: <20240829155950.1141978-1-andriy.shevchenko@linux.intel.com>
On Thu, 29 Aug 2024, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> With CONFIG_WERROR=y and `make W=1` build fails on my x86_64 machine.
> This is due to some unused functions. Hence these quick fixes.
Since when have we been getting the warnings for static inlines?
BR,
Jani.
>
> Andy Shevchenko (2):
> drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused
> drm/i915/fence: Mark debug_fence_free() with __maybe_unused
>
> drivers/gpu/drm/i915/i915_sw_fence.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-08-29 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 15:58 [PATCH v1 0/2] drm/i915/fence: A couple of build fixes Andy Shevchenko
2024-08-29 15:58 ` [PATCH v1 1/2] drm/i915/fence: Mark debug_fence_init_onstack() with __maybe_unused Andy Shevchenko
2024-08-29 15:58 ` [PATCH v1 2/2] drm/i915/fence: Mark debug_fence_free() " Andy Shevchenko
2024-08-29 16:38 ` Jani Nikula [this message]
2024-08-29 16:53 ` [PATCH v1 0/2] drm/i915/fence: A couple of build fixes Andy Shevchenko
2024-08-29 18:10 ` Andy Shevchenko
2024-08-29 18:22 ` Nathan Chancellor
2024-08-29 18:37 ` Jani Nikula
2024-08-29 20:03 ` Nathan Chancellor
2024-09-02 8:27 ` Jani Nikula
2024-09-02 10:20 ` Andy Shevchenko
2024-08-29 17:03 ` ✗ Fi.CI.BUILD: warning for " Patchwork
2024-08-29 17:17 ` ✓ Fi.CI.BAT: success " Patchwork
2024-08-31 0:49 ` ✓ Fi.CI.IGT: " 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=87cylrwahb.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel@ffwll.ch \
--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=rodrigo.vivi@intel.com \
--cc=tursulin@ursulin.net \
/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.