From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: Signed-off-by missing for commits in the drm-msm-lumag tree
Date: Fri, 10 Mar 2023 14:01:11 +1100 [thread overview]
Message-ID: <20230310140111.6843985b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Hi all,
Commits
7eaace06eaaa ("drm/msm/dp: set self refresh aware based on PSR support")
22459a50890f ("drm/msm/disp/dpu: update dpu_enc crtc state on crtc enable/disable during self refresh")
31c98355c44e ("drm/msm/disp/dpu: add PSR support for eDP interface in dpu driver")
e57669adb9c9 ("drm/msm/disp/dpu: use atomic enable/disable callbacks for encoder functions")
94d3b11ccbf0 ("drm/msm/dp: use the eDP bridge ops to validate eDP modes")
0b2997e060cc ("drm/msm/dp: Add basic PSR support for eDP")
884ad965b6df ("drm/msm/dp: use atomic callbacks for DP bridge ops")
acb0c11f657d ("drm/msm/disp/dpu: reset the datapath after timing engine disable")
9cc249dfddab ("drm/msm/disp/dpu: wait for extra vsync till timing engine status is disabled")
8a9ca0105519 ("drm/msm/disp/dpu: get timing engine status from intf status register")
01733a9d3510 ("drm/msm/disp/dpu: check for crtc enable rather than crtc active to release shared resources")
7a4d735b3fca ("drm/bridge: add psr support for panel bridge callbacks")
afed6525a251 ("drm/bridge: use atomic enable/disable callbacks for panel bridge")
52e6ac96e351 ("drm: add helper functions to retrieve old and new crtc")
are missing a Signed-off-by from their committer.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2023-03-10 3:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230310140111.6843985b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dmitry.baryshkov@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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