From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Rob Clark <robdclark@gmail•com>, Sean Paul <seanpaul@chromium•org>
Cc: Jun Nie <jun.nie@linaro•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Fixes tag needs some work in the drm-msm-fixes tree
Date: Tue, 15 Apr 2025 08:04:46 +1000 [thread overview]
Message-ID: <20250415080446.50f232a1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 350 bytes --]
Hi all,
In commit
bcaa391e177c ("drm/msm/dpu: check every pipe per capability")
Fixes tag
Fixes: ("dbbf57dfd04e6 drm/msm/dpu: split dpu_plane_atomic_check()")
has these problem(s):
- No SHA1 recognised
It should be:
Fixes: dbbf57dfd04e6 ("drm/msm/dpu: split dpu_plane_atomic_check()")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-04-14 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 22:04 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-09 22:14 linux-next: Fixes tag needs some work in the drm-msm-fixes tree Stephen Rothwell
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=20250415080446.50f232a1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jun.nie@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=robdclark@gmail$(echo .)com \
--cc=seanpaul@chromium$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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