All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kuogee Hsieh <quic_khsieh@quicinc.com>,
	dri-devel@lists.freedesktop.org, robdclark@gmail.com,
	sean@poorly.run, swboyd@chromium.org, dianders@chromium.org,
	vkoul@kernel.org, daniel@ffwll.ch, airlied@gmail.com,
	agross@kernel.org, dmitry.baryshkov@linaro.org,
	andersson@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, quic_sbillaka@quicinc.com,
	linux-arm-msm@vger.kernel.org, quic_abhinavk@quicinc.com,
	Kuogee Hsieh <quic_khsieh@quicinc.com>,
	marijn.suijten@somainline.org, quic_jesszhan@quicinc.com,
	freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/7] drm/msm/dp: incorporate pm_runtime framework into DP driver
Date: Sat, 16 Sep 2023 13:25:23 +0800	[thread overview]
Message-ID: <202309161321.UeiYRcIs-lkp@intel.com> (raw)
In-Reply-To: <1694813901-26952-5-git-send-email-quic_khsieh@quicinc.com>

Hi Kuogee,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes linus/master v6.6-rc1]
[cannot apply to drm-misc/drm-misc-next drm-tip/drm-tip next-20230915]
[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/Kuogee-Hsieh/drm-msm-dp-tie-dp_display_irq_handler-with-dp-driver/20230916-054014
base:   git://anongit.freedesktop.org/drm/drm drm-next
patch link:    https://lore.kernel.org/r/1694813901-26952-5-git-send-email-quic_khsieh%40quicinc.com
patch subject: [PATCH v3 4/7] drm/msm/dp: incorporate pm_runtime framework into DP driver
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20230916/202309161321.UeiYRcIs-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230916/202309161321.UeiYRcIs-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/202309161321.UeiYRcIs-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/gpu/drm/msm/dp/dp_power.c: In function 'dp_power_client_deinit':
>> drivers/gpu/drm/msm/dp/dp_power.c:160:34: warning: variable 'power' set but not used [-Wunused-but-set-variable]
     160 |         struct dp_power_private *power;
         |                                  ^~~~~
   drivers/gpu/drm/msm/dp/dp_power.c: In function 'dp_power_init':
   drivers/gpu/drm/msm/dp/dp_power.c:168:34: warning: variable 'power' set but not used [-Wunused-but-set-variable]
     168 |         struct dp_power_private *power = NULL;
         |                                  ^~~~~
   drivers/gpu/drm/msm/dp/dp_power.c: In function 'dp_power_deinit':
   drivers/gpu/drm/msm/dp/dp_power.c:179:34: warning: variable 'power' set but not used [-Wunused-but-set-variable]
     179 |         struct dp_power_private *power;
         |                                  ^~~~~


vim +/power +160 drivers/gpu/drm/msm/dp/dp_power.c

c943b4948b5848 Chandan Uddaraju 2020-08-27  157  
c943b4948b5848 Chandan Uddaraju 2020-08-27  158  void dp_power_client_deinit(struct dp_power *dp_power)
c943b4948b5848 Chandan Uddaraju 2020-08-27  159  {
c943b4948b5848 Chandan Uddaraju 2020-08-27 @160  	struct dp_power_private *power;
c943b4948b5848 Chandan Uddaraju 2020-08-27  161  
c943b4948b5848 Chandan Uddaraju 2020-08-27  162  	power = container_of(dp_power, struct dp_power_private, dp_power);
c943b4948b5848 Chandan Uddaraju 2020-08-27  163  }
c943b4948b5848 Chandan Uddaraju 2020-08-27  164  

-- 
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: Kuogee Hsieh <quic_khsieh@quicinc.com>,
	dri-devel@lists.freedesktop.org, robdclark@gmail.com,
	sean@poorly.run, swboyd@chromium.org, dianders@chromium.org,
	vkoul@kernel.org, daniel@ffwll.ch, airlied@gmail.com,
	agross@kernel.org, dmitry.baryshkov@linaro.org,
	andersson@kernel.org
Cc: quic_sbillaka@quicinc.com, quic_jesszhan@quicinc.com,
	linux-arm-msm@vger.kernel.org, quic_abhinavk@quicinc.com,
	Kuogee Hsieh <quic_khsieh@quicinc.com>,
	oe-kbuild-all@lists.linux.dev, marijn.suijten@somainline.org,
	freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/7] drm/msm/dp: incorporate pm_runtime framework into DP driver
Date: Sat, 16 Sep 2023 13:25:23 +0800	[thread overview]
Message-ID: <202309161321.UeiYRcIs-lkp@intel.com> (raw)
In-Reply-To: <1694813901-26952-5-git-send-email-quic_khsieh@quicinc.com>

Hi Kuogee,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes linus/master v6.6-rc1]
[cannot apply to drm-misc/drm-misc-next drm-tip/drm-tip next-20230915]
[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/Kuogee-Hsieh/drm-msm-dp-tie-dp_display_irq_handler-with-dp-driver/20230916-054014
base:   git://anongit.freedesktop.org/drm/drm drm-next
patch link:    https://lore.kernel.org/r/1694813901-26952-5-git-send-email-quic_khsieh%40quicinc.com
patch subject: [PATCH v3 4/7] drm/msm/dp: incorporate pm_runtime framework into DP driver
config: sparc-allyesconfig (https://download.01.org/0day-ci/archive/20230916/202309161321.UeiYRcIs-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230916/202309161321.UeiYRcIs-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/202309161321.UeiYRcIs-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/gpu/drm/msm/dp/dp_power.c: In function 'dp_power_client_deinit':
>> drivers/gpu/drm/msm/dp/dp_power.c:160:34: warning: variable 'power' set but not used [-Wunused-but-set-variable]
     160 |         struct dp_power_private *power;
         |                                  ^~~~~
   drivers/gpu/drm/msm/dp/dp_power.c: In function 'dp_power_init':
   drivers/gpu/drm/msm/dp/dp_power.c:168:34: warning: variable 'power' set but not used [-Wunused-but-set-variable]
     168 |         struct dp_power_private *power = NULL;
         |                                  ^~~~~
   drivers/gpu/drm/msm/dp/dp_power.c: In function 'dp_power_deinit':
   drivers/gpu/drm/msm/dp/dp_power.c:179:34: warning: variable 'power' set but not used [-Wunused-but-set-variable]
     179 |         struct dp_power_private *power;
         |                                  ^~~~~


vim +/power +160 drivers/gpu/drm/msm/dp/dp_power.c

c943b4948b5848 Chandan Uddaraju 2020-08-27  157  
c943b4948b5848 Chandan Uddaraju 2020-08-27  158  void dp_power_client_deinit(struct dp_power *dp_power)
c943b4948b5848 Chandan Uddaraju 2020-08-27  159  {
c943b4948b5848 Chandan Uddaraju 2020-08-27 @160  	struct dp_power_private *power;
c943b4948b5848 Chandan Uddaraju 2020-08-27  161  
c943b4948b5848 Chandan Uddaraju 2020-08-27  162  	power = container_of(dp_power, struct dp_power_private, dp_power);
c943b4948b5848 Chandan Uddaraju 2020-08-27  163  }
c943b4948b5848 Chandan Uddaraju 2020-08-27  164  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2023-09-16  5:27 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 21:38 [PATCH v3 0/7] incorporate pm runtime framework and eDP clean up Kuogee Hsieh
2023-09-15 21:38 ` Kuogee Hsieh
2023-09-15 21:38 ` [PATCH v3 1/7] drm/msm/dp: tie dp_display_irq_handler() with dp driver Kuogee Hsieh
2023-09-15 21:38   ` Kuogee Hsieh
2023-09-16  0:29   ` Dmitry Baryshkov
2023-09-16  0:29     ` Dmitry Baryshkov
2023-09-18 17:02     ` Kuogee Hsieh
2023-09-18 17:02       ` Kuogee Hsieh
2023-09-19  9:44       ` Dmitry Baryshkov
2023-09-19  9:44         ` Dmitry Baryshkov
2023-09-22 23:02     ` Kuogee Hsieh
2023-09-22 23:02       ` Kuogee Hsieh
2023-09-23 18:45       ` Dmitry Baryshkov
2023-09-23 18:45         ` Dmitry Baryshkov
2023-09-27 15:25         ` Kuogee Hsieh
2023-09-27 15:25           ` Kuogee Hsieh
2023-09-15 21:38 ` [PATCH v3 2/7] drm/msm/dp: replace is_connected with link_ready Kuogee Hsieh
2023-09-15 21:38   ` Kuogee Hsieh
2023-09-16  1:51   ` Dmitry Baryshkov
2023-09-16  1:51     ` Dmitry Baryshkov
2023-09-18 17:09     ` Kuogee Hsieh
2023-09-18 17:09       ` Kuogee Hsieh
2023-09-19  9:44       ` Dmitry Baryshkov
2023-09-19  9:44         ` Dmitry Baryshkov
2023-09-15 21:38 ` [PATCH v3 3/7] drm/msm/dp: use drm_bridge_hpd_notify() to report HPD status changes Kuogee Hsieh
2023-09-15 21:38   ` Kuogee Hsieh
2023-09-16  0:41   ` Dmitry Baryshkov
2023-09-16  0:41     ` Dmitry Baryshkov
2023-09-18 20:16     ` Kuogee Hsieh
2023-09-18 20:16       ` Kuogee Hsieh
2023-09-19  9:45       ` Dmitry Baryshkov
2023-09-19  9:45         ` Dmitry Baryshkov
2023-09-15 21:38 ` [PATCH v3 4/7] drm/msm/dp: incorporate pm_runtime framework into DP driver Kuogee Hsieh
2023-09-15 21:38   ` Kuogee Hsieh
2023-09-16  1:07   ` Dmitry Baryshkov
2023-09-16  1:07     ` Dmitry Baryshkov
2023-09-20 22:46     ` Kuogee Hsieh
2023-09-20 22:46       ` Kuogee Hsieh
2023-09-25  9:06       ` Dmitry Baryshkov
2023-09-25  9:06         ` Dmitry Baryshkov
2023-09-16  5:25   ` kernel test robot [this message]
2023-09-16  5:25     ` kernel test robot
2023-09-15 21:38 ` [PATCH v3 5/7] drm/msm/dp: delete EV_HPD_INIT_SETUP Kuogee Hsieh
2023-09-15 21:38   ` Kuogee Hsieh
2023-09-16  1:09   ` Dmitry Baryshkov
2023-09-16  1:09     ` Dmitry Baryshkov
2023-09-15 21:38 ` [PATCH v3 6/7] drm/msm/dp: add pm_runtime_force_suspend()/resume() Kuogee Hsieh
2023-09-15 21:38   ` Kuogee Hsieh
2023-09-16  1:21   ` Dmitry Baryshkov
2023-09-16  1:21     ` Dmitry Baryshkov
2023-09-18 17:47     ` Kuogee Hsieh
2023-09-18 17:47       ` Kuogee Hsieh
2023-09-19  9:50       ` Dmitry Baryshkov
2023-09-19  9:50         ` Dmitry Baryshkov
2023-09-20 19:49         ` Kuogee Hsieh
2023-09-20 19:49           ` Kuogee Hsieh
2023-09-22 21:54         ` Stephen Boyd
2023-09-22 21:54           ` Stephen Boyd
2023-09-23  1:35           ` Abhinav Kumar
2023-09-23  1:35             ` Abhinav Kumar
2023-09-25 16:07             ` Kuogee Hsieh
2023-09-25 16:07               ` Kuogee Hsieh
2023-09-27 22:01               ` Stephen Boyd
2023-09-27 22:01                 ` Stephen Boyd
2023-09-27 22:04                 ` Dmitry Baryshkov
2023-09-27 22:04                   ` Dmitry Baryshkov
2023-09-29  0:46                 ` Abhinav Kumar
2023-09-29  0:46                   ` Abhinav Kumar
2023-10-02 22:58                   ` Stephen Boyd
2023-10-02 22:58                     ` Stephen Boyd
2023-10-03  1:32                     ` Abhinav Kumar
2023-10-03  1:32                       ` Abhinav Kumar
2023-10-03  8:00                       ` Dmitry Baryshkov
2023-10-03  8:00                         ` Dmitry Baryshkov
2023-09-27 21:41             ` Stephen Boyd
2023-09-27 21:41               ` Stephen Boyd
2023-09-28 22:35               ` Abhinav Kumar
2023-09-28 22:35                 ` Abhinav Kumar
2023-09-15 21:38 ` [PATCH v3 7/7] drm/msm/dp: move of_dp_aux_populate_bus() to eDP probe() Kuogee Hsieh
2023-09-15 21:38   ` Kuogee Hsieh
2023-09-16  1:48   ` Dmitry Baryshkov
2023-09-16  1:48     ` 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=202309161321.UeiYRcIs-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=agross@kernel.org \
    --cc=airlied@gmail.com \
    --cc=andersson@kernel.org \
    --cc=daniel@ffwll.ch \
    --cc=dianders@chromium.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=quic_abhinavk@quicinc.com \
    --cc=quic_jesszhan@quicinc.com \
    --cc=quic_khsieh@quicinc.com \
    --cc=quic_sbillaka@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=sean@poorly.run \
    --cc=swboyd@chromium.org \
    --cc=vkoul@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.