From: kernel test robot <lkp@intel.com>
To: Lucas Stach <l.stach@pengutronix.de>, Marek Vasut <marex@denx.de>,
Liu Ying <victor.liu@nxp.com>
Cc: oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
patchwork-lst@pengutronix.de
Subject: Re: [PATCH v2 3/6] drm: lcdif: rework runtime PM handling in the atomic commit
Date: Fri, 22 Sep 2023 05:32:30 +0800 [thread overview]
Message-ID: <202309220530.84SlbdTU-lkp@intel.com> (raw)
In-Reply-To: <20230921200312.3989073-3-l.stach@pengutronix.de>
Hi Lucas,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on linus/master v6.6-rc2 next-20230921]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Lucas-Stach/drm-lcdif-don-t-clear-unrelated-bits-in-CTRLDESCL0_5-when-setting-up-format/20230922-040438
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20230921200312.3989073-3-l.stach%40pengutronix.de
patch subject: [PATCH v2 3/6] drm: lcdif: rework runtime PM handling in the atomic commit
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20230922/202309220530.84SlbdTU-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230922/202309220530.84SlbdTU-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309220530.84SlbdTU-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/mxsfb/lcdif_drv.c:39:6: warning: no previous prototype for 'lcdif_commit_tail' [-Wmissing-prototypes]
39 | void lcdif_commit_tail(struct drm_atomic_state *old_state)
| ^~~~~~~~~~~~~~~~~
vim +/lcdif_commit_tail +39 drivers/gpu/drm/mxsfb/lcdif_drv.c
38
> 39 void lcdif_commit_tail(struct drm_atomic_state *old_state)
40 {
41 struct drm_device *drm = old_state->dev;
42
43 pm_runtime_get_sync(drm->dev);
44
45 drm_atomic_helper_commit_modeset_disables(drm, old_state);
46 drm_atomic_helper_commit_planes(drm, old_state,
47 DRM_PLANE_COMMIT_ACTIVE_ONLY);
48 drm_atomic_helper_commit_modeset_enables(drm, old_state);
49
50 drm_atomic_helper_fake_vblank(old_state);
51 drm_atomic_helper_commit_hw_done(old_state);
52 drm_atomic_helper_wait_for_vblanks(drm, old_state);
53
54 pm_runtime_put(drm->dev);
55
56 drm_atomic_helper_cleanup_planes(drm, old_state);
57 }
58
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-09-21 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 20:03 [PATCH v2 1/6] drm: lcdif: improve burst size configuration comment Lucas Stach
2023-09-21 20:03 ` [PATCH v2 2/6] drm: lcdif: don't clear unrelated bits in CTRLDESCL0_5 when setting up format Lucas Stach
2023-09-21 20:03 ` [PATCH v2 3/6] drm: lcdif: rework runtime PM handling in the atomic commit Lucas Stach
2023-09-21 21:32 ` kernel test robot [this message]
2023-09-22 9:51 ` Ying Liu
2023-09-22 14:33 ` Lucas Stach
2023-09-21 20:03 ` [PATCH v2 4/6] drm: lcdif: remove superfluous setup of framebuffer DMA address Lucas Stach
2023-09-21 20:03 ` [PATCH v2 5/6] drm: lcdif: move pitch setup to plane atomic update Lucas Stach
2023-09-21 20:03 ` [PATCH v2 6/6] drm: lcdif: force modeset when FB format changes Lucas Stach
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=202309220530.84SlbdTU-lkp@intel.com \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marex@denx.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=patchwork-lst@pengutronix.de \
--cc=victor.liu@nxp.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).