From: Jani Nikula <jani.nikula@intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm: enable warnings on unused static inlines
Date: Tue, 10 Sep 2024 13:05:50 +0300 [thread overview]
Message-ID: <87zfofkem9.fsf@intel.com> (raw)
In-Reply-To: <87seuer1we.fsf@intel.com>
On Thu, 05 Sep 2024, Jani Nikula <jani.nikula@intel.com> wrote:
> On Wed, 04 Sep 2024, Nathan Chancellor <nathan@kernel.org> wrote:
>> I ran this through my test matrix and this is what it found (across
>> various configuration options, I can give specifics as necessary):
>
> Thanks, I didn't really expect this would not catch anything. :)
>
> We've already fixed some in drm-misc-next and drm-intel-next, see
> below. Will need to fix more before merging, obviously.
New try with fixes at [1]. Fingers crossed.
BR,
Jani.
[1] https://lore.kernel.org/r/cover.1725962479.git.jani.nikula@intel.com
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-09-10 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 12:38 [PATCH] drm: enable warnings on unused static inlines Jani Nikula
2024-09-04 12:55 ` ✓ CI.Patch_applied: success for " Patchwork
2024-09-04 12:55 ` ✓ CI.checkpatch: " Patchwork
2024-09-04 12:56 ` ✓ CI.KUnit: " Patchwork
2024-09-04 13:08 ` ✓ CI.Build: " Patchwork
2024-09-04 13:10 ` ✓ CI.Hooks: " Patchwork
2024-09-04 13:12 ` ✗ CI.checksparse: warning " Patchwork
2024-09-04 13:18 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-09-04 13:33 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-04 22:30 ` [PATCH] " Nathan Chancellor
2024-09-05 7:32 ` Jani Nikula
2024-09-10 10:05 ` Jani Nikula [this message]
2024-09-05 12:18 ` ✗ Fi.CI.IGT: failure for " Patchwork
2024-09-06 14:38 ` ✓ CI.FULL: success " 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=87zfofkem9.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=nathan@kernel.org \
/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.