From: kernel test robot <lkp@intel.com>
To: Marek Vasut <marex@denx.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Andrzej Hajda <andrzej.hajda@intel.com>
Subject: [drm-misc:for-linux-next 10/10] drivers/gpu/drm/rcar-du/rcar_mipi_dsi.c:683:13: warning: unused variable 'data_lanes'
Date: Sun, 12 Jun 2022 20:48:52 +0800 [thread overview]
Message-ID: <202206122009.urQLG05k-lkp@intel.com> (raw)
tree: git://anongit.freedesktop.org/drm/drm-misc for-linux-next
head: d643daaf1694b7565fbe3982b630e1c7b95f1600
commit: d643daaf1694b7565fbe3982b630e1c7b95f1600 [10/10] drm/bridge: rcar: Convert to drm_of_get_data_lanes_count_ep
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220612/202206122009.urQLG05k-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
git remote add drm-misc git://anongit.freedesktop.org/drm/drm-misc
git fetch --no-tags drm-misc for-linux-next
git checkout d643daaf1694b7565fbe3982b630e1c7b95f1600
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/rcar-du/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/gpu/drm/rcar-du/rcar_mipi_dsi.c: In function 'rcar_mipi_dsi_parse_dt':
>> drivers/gpu/drm/rcar-du/rcar_mipi_dsi.c:683:13: warning: unused variable 'data_lanes' [-Wunused-variable]
683 | u32 data_lanes[4];
| ^~~~~~~~~~
>> drivers/gpu/drm/rcar-du/rcar_mipi_dsi.c:682:29: warning: unused variable 'ep' [-Wunused-variable]
682 | struct device_node *ep;
| ^~
vim +/data_lanes +683 drivers/gpu/drm/rcar-du/rcar_mipi_dsi.c
155358310f013c LUU HOAI 2020-02-25 675
155358310f013c LUU HOAI 2020-02-25 676 /* -----------------------------------------------------------------------------
155358310f013c LUU HOAI 2020-02-25 677 * Probe & Remove
155358310f013c LUU HOAI 2020-02-25 678 */
155358310f013c LUU HOAI 2020-02-25 679
155358310f013c LUU HOAI 2020-02-25 680 static int rcar_mipi_dsi_parse_dt(struct rcar_mipi_dsi *dsi)
155358310f013c LUU HOAI 2020-02-25 681 {
155358310f013c LUU HOAI 2020-02-25 @682 struct device_node *ep;
155358310f013c LUU HOAI 2020-02-25 @683 u32 data_lanes[4];
155358310f013c LUU HOAI 2020-02-25 684 int ret;
155358310f013c LUU HOAI 2020-02-25 685
d643daaf1694b7 Marek Vasut 2022-05-24 686 ret = drm_of_get_data_lanes_count_ep(dsi->dev->of_node, 1, 0, 1, 4);
155358310f013c LUU HOAI 2020-02-25 687 if (ret < 0) {
155358310f013c LUU HOAI 2020-02-25 688 dev_err(dsi->dev, "missing or invalid data-lanes property\n");
d643daaf1694b7 Marek Vasut 2022-05-24 689 return ret;
155358310f013c LUU HOAI 2020-02-25 690 }
155358310f013c LUU HOAI 2020-02-25 691
155358310f013c LUU HOAI 2020-02-25 692 dsi->num_data_lanes = ret;
155358310f013c LUU HOAI 2020-02-25 693 return 0;
155358310f013c LUU HOAI 2020-02-25 694 }
155358310f013c LUU HOAI 2020-02-25 695
:::::: The code at line 683 was first introduced by commit
:::::: 155358310f013c23c2e5533e007afc7310c9a964 drm: rcar-du: Add R-Car DSI driver
:::::: TO: LUU HOAI <hoai.luu.ub@renesas.com>
:::::: CC: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-12 12:50 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=202206122009.urQLG05k-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrzej.hajda@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox