From: kernel test robot <lkp@intel.com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rodrigo Siqueira" <rodrigosiqueiramelo@gmail.com>,
"Melissa Wen" <melissa.srw@gmail.com>,
"Maíra Canal" <mairacanal@riseup.net>,
"Haneen Mohammed" <hamohammed.sa@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/2] drm/atomic-helper: rename drm_atomic_helper_check_wb_encoder_state
Date: Tue, 5 Dec 2023 19:04:30 +0800 [thread overview]
Message-ID: <202312051810.e0QCZPbY-lkp@intel.com> (raw)
In-Reply-To: <20231205023150.1581875-2-dmitry.baryshkov@linaro.org>
Hi Dmitry,
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.7-rc4 next-20231205]
[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/Dmitry-Baryshkov/drm-atomic-helper-rename-drm_atomic_helper_check_wb_encoder_state/20231205-103552
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20231205023150.1581875-2-dmitry.baryshkov%40linaro.org
patch subject: [PATCH v2 1/2] drm/atomic-helper: rename drm_atomic_helper_check_wb_encoder_state
config: i386-buildonly-randconfig-003-20231205 (https://download.01.org/0day-ci/archive/20231205/202312051810.e0QCZPbY-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231205/202312051810.e0QCZPbY-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/202312051810.e0QCZPbY-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/drm_atomic_helper.c:811: warning: Function parameter or member 'wb_conn' not described in 'drm_atomic_helper_check_wb_connector_state'
>> drivers/gpu/drm/drm_atomic_helper.c:811: warning: Excess function parameter 'connector' description in 'drm_atomic_helper_check_wb_connector_state'
vim +811 drivers/gpu/drm/drm_atomic_helper.c
623369e533e8a5 Daniel Vetter 2014-09-16 796
254fe9c106ed69 Igor Torrente 2022-09-05 797 /**
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 798 * drm_atomic_helper_check_wb_connector_state() - Check writeback connector state
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 799 * @connector: corresponding connector
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 800 * @state: the driver state object
254fe9c106ed69 Igor Torrente 2022-09-05 801 *
254fe9c106ed69 Igor Torrente 2022-09-05 802 * Checks if the writeback connector state is valid, and returns an error if it
254fe9c106ed69 Igor Torrente 2022-09-05 803 * isn't.
254fe9c106ed69 Igor Torrente 2022-09-05 804 *
254fe9c106ed69 Igor Torrente 2022-09-05 805 * RETURNS:
254fe9c106ed69 Igor Torrente 2022-09-05 806 * Zero for success or -errno
254fe9c106ed69 Igor Torrente 2022-09-05 807 */
254fe9c106ed69 Igor Torrente 2022-09-05 808 int
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 809 drm_atomic_helper_check_wb_connector_state(struct drm_writeback_connector *wb_conn,
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 810 struct drm_atomic_state *state)
254fe9c106ed69 Igor Torrente 2022-09-05 @811 {
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 812 struct drm_connector_state *conn_state =
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 813 drm_atomic_get_new_connector_state(state, &wb_conn->base);
254fe9c106ed69 Igor Torrente 2022-09-05 814 struct drm_writeback_job *wb_job = conn_state->writeback_job;
254fe9c106ed69 Igor Torrente 2022-09-05 815 struct drm_property_blob *pixel_format_blob;
254fe9c106ed69 Igor Torrente 2022-09-05 816 struct drm_framebuffer *fb;
254fe9c106ed69 Igor Torrente 2022-09-05 817 size_t i, nformats;
254fe9c106ed69 Igor Torrente 2022-09-05 818 u32 *formats;
254fe9c106ed69 Igor Torrente 2022-09-05 819
254fe9c106ed69 Igor Torrente 2022-09-05 820 if (!wb_job || !wb_job->fb)
254fe9c106ed69 Igor Torrente 2022-09-05 821 return 0;
254fe9c106ed69 Igor Torrente 2022-09-05 822
254fe9c106ed69 Igor Torrente 2022-09-05 823 pixel_format_blob = wb_job->connector->pixel_formats_blob_ptr;
254fe9c106ed69 Igor Torrente 2022-09-05 824 nformats = pixel_format_blob->length / sizeof(u32);
254fe9c106ed69 Igor Torrente 2022-09-05 825 formats = pixel_format_blob->data;
254fe9c106ed69 Igor Torrente 2022-09-05 826 fb = wb_job->fb;
254fe9c106ed69 Igor Torrente 2022-09-05 827
254fe9c106ed69 Igor Torrente 2022-09-05 828 for (i = 0; i < nformats; i++)
254fe9c106ed69 Igor Torrente 2022-09-05 829 if (fb->format->format == formats[i])
254fe9c106ed69 Igor Torrente 2022-09-05 830 return 0;
254fe9c106ed69 Igor Torrente 2022-09-05 831
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 832 drm_dbg_kms(wb_conn->base.dev, "Invalid pixel format %p4cc\n", &fb->format->format);
254fe9c106ed69 Igor Torrente 2022-09-05 833
254fe9c106ed69 Igor Torrente 2022-09-05 834 return -EINVAL;
254fe9c106ed69 Igor Torrente 2022-09-05 835 }
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 836 EXPORT_SYMBOL(drm_atomic_helper_check_wb_connector_state);
254fe9c106ed69 Igor Torrente 2022-09-05 837
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: "Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Rodrigo Siqueira" <rodrigosiqueiramelo@gmail.com>,
"Melissa Wen" <melissa.srw@gmail.com>,
"Maíra Canal" <mairacanal@riseup.net>,
"Haneen Mohammed" <hamohammed.sa@gmail.com>
Cc: linux-arm-msm@vger.kernel.org, freedreno@lists.freedesktop.org,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
dri-devel@lists.freedesktop.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 1/2] drm/atomic-helper: rename drm_atomic_helper_check_wb_encoder_state
Date: Tue, 5 Dec 2023 19:04:30 +0800 [thread overview]
Message-ID: <202312051810.e0QCZPbY-lkp@intel.com> (raw)
In-Reply-To: <20231205023150.1581875-2-dmitry.baryshkov@linaro.org>
Hi Dmitry,
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.7-rc4 next-20231205]
[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/Dmitry-Baryshkov/drm-atomic-helper-rename-drm_atomic_helper_check_wb_encoder_state/20231205-103552
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20231205023150.1581875-2-dmitry.baryshkov%40linaro.org
patch subject: [PATCH v2 1/2] drm/atomic-helper: rename drm_atomic_helper_check_wb_encoder_state
config: i386-buildonly-randconfig-003-20231205 (https://download.01.org/0day-ci/archive/20231205/202312051810.e0QCZPbY-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231205/202312051810.e0QCZPbY-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/202312051810.e0QCZPbY-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/drm_atomic_helper.c:811: warning: Function parameter or member 'wb_conn' not described in 'drm_atomic_helper_check_wb_connector_state'
>> drivers/gpu/drm/drm_atomic_helper.c:811: warning: Excess function parameter 'connector' description in 'drm_atomic_helper_check_wb_connector_state'
vim +811 drivers/gpu/drm/drm_atomic_helper.c
623369e533e8a5 Daniel Vetter 2014-09-16 796
254fe9c106ed69 Igor Torrente 2022-09-05 797 /**
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 798 * drm_atomic_helper_check_wb_connector_state() - Check writeback connector state
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 799 * @connector: corresponding connector
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 800 * @state: the driver state object
254fe9c106ed69 Igor Torrente 2022-09-05 801 *
254fe9c106ed69 Igor Torrente 2022-09-05 802 * Checks if the writeback connector state is valid, and returns an error if it
254fe9c106ed69 Igor Torrente 2022-09-05 803 * isn't.
254fe9c106ed69 Igor Torrente 2022-09-05 804 *
254fe9c106ed69 Igor Torrente 2022-09-05 805 * RETURNS:
254fe9c106ed69 Igor Torrente 2022-09-05 806 * Zero for success or -errno
254fe9c106ed69 Igor Torrente 2022-09-05 807 */
254fe9c106ed69 Igor Torrente 2022-09-05 808 int
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 809 drm_atomic_helper_check_wb_connector_state(struct drm_writeback_connector *wb_conn,
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 810 struct drm_atomic_state *state)
254fe9c106ed69 Igor Torrente 2022-09-05 @811 {
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 812 struct drm_connector_state *conn_state =
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 813 drm_atomic_get_new_connector_state(state, &wb_conn->base);
254fe9c106ed69 Igor Torrente 2022-09-05 814 struct drm_writeback_job *wb_job = conn_state->writeback_job;
254fe9c106ed69 Igor Torrente 2022-09-05 815 struct drm_property_blob *pixel_format_blob;
254fe9c106ed69 Igor Torrente 2022-09-05 816 struct drm_framebuffer *fb;
254fe9c106ed69 Igor Torrente 2022-09-05 817 size_t i, nformats;
254fe9c106ed69 Igor Torrente 2022-09-05 818 u32 *formats;
254fe9c106ed69 Igor Torrente 2022-09-05 819
254fe9c106ed69 Igor Torrente 2022-09-05 820 if (!wb_job || !wb_job->fb)
254fe9c106ed69 Igor Torrente 2022-09-05 821 return 0;
254fe9c106ed69 Igor Torrente 2022-09-05 822
254fe9c106ed69 Igor Torrente 2022-09-05 823 pixel_format_blob = wb_job->connector->pixel_formats_blob_ptr;
254fe9c106ed69 Igor Torrente 2022-09-05 824 nformats = pixel_format_blob->length / sizeof(u32);
254fe9c106ed69 Igor Torrente 2022-09-05 825 formats = pixel_format_blob->data;
254fe9c106ed69 Igor Torrente 2022-09-05 826 fb = wb_job->fb;
254fe9c106ed69 Igor Torrente 2022-09-05 827
254fe9c106ed69 Igor Torrente 2022-09-05 828 for (i = 0; i < nformats; i++)
254fe9c106ed69 Igor Torrente 2022-09-05 829 if (fb->format->format == formats[i])
254fe9c106ed69 Igor Torrente 2022-09-05 830 return 0;
254fe9c106ed69 Igor Torrente 2022-09-05 831
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 832 drm_dbg_kms(wb_conn->base.dev, "Invalid pixel format %p4cc\n", &fb->format->format);
254fe9c106ed69 Igor Torrente 2022-09-05 833
254fe9c106ed69 Igor Torrente 2022-09-05 834 return -EINVAL;
254fe9c106ed69 Igor Torrente 2022-09-05 835 }
d538670e1a27f5 Dmitry Baryshkov 2023-12-05 836 EXPORT_SYMBOL(drm_atomic_helper_check_wb_connector_state);
254fe9c106ed69 Igor Torrente 2022-09-05 837
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-05 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 2:31 [PATCH v2 0/2] drm/atomic-helper: rename drm_atomic_helper_check_wb_encoder_state Dmitry Baryshkov
2023-12-05 2:31 ` Dmitry Baryshkov
2023-12-05 2:31 ` [PATCH v2 1/2] " Dmitry Baryshkov
2023-12-05 2:31 ` Dmitry Baryshkov
2023-12-05 11:04 ` kernel test robot [this message]
2023-12-05 11:04 ` kernel test robot
2023-12-05 2:31 ` [PATCH v2 2/2] drm/vkms: move wb's atomic_check from encoder to connector Dmitry Baryshkov
2023-12-05 2:31 ` Dmitry Baryshkov
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=202312051810.e0QCZPbY-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mairacanal@riseup.net \
--cc=melissa.srw@gmail.com \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_abhinavk@quicinc.com \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=tzimmermann@suse.de \
/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.