mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Zeng Heng <zengheng4@huawei.com>,
	bp@suse.de, javierm@redhat.com, ardb@kernel.org,
	tzimmermann@suse.de, simona.vetter@ffwll.ch
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	bobo.shaobowang@huawei.com, linux-efi@vger.kernel.org
Subject: Re: [PATCH] drivers/firmware: Fix unused const variable 'efifb_fwnode_ops'
Date: Fri, 25 Oct 2024 13:03:22 +0800	[thread overview]
Message-ID: <202410251211.Jze0KkZR-lkp@intel.com> (raw)
In-Reply-To: <20241024084435.165333-1-zengheng4@huawei.com>

Hi Zeng,

kernel test robot noticed the following build warnings:

[auto build test WARNING on efi/next]
[also build test WARNING on linus/master v6.12-rc4 next-20241024]
[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/Zeng-Heng/drivers-firmware-Fix-unused-const-variable-efifb_fwnode_ops/20241024-163259
base:   https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git next
patch link:    https://lore.kernel.org/r/20241024084435.165333-1-zengheng4%40huawei.com
patch subject: [PATCH] drivers/firmware: Fix unused const variable 'efifb_fwnode_ops'
config: x86_64-buildonly-randconfig-002-20241025 (https://download.01.org/0day-ci/archive/20241025/202410251211.Jze0KkZR-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241025/202410251211.Jze0KkZR-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/202410251211.Jze0KkZR-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/firmware/efi/sysfb_efi.c:328:12: warning: 'efifb_add_links' defined but not used [-Wunused-function]
     328 | static int efifb_add_links(struct fwnode_handle *fwnode)
         |            ^~~~~~~~~~~~~~~
>> drivers/firmware/efi/sysfb_efi.c:94:19: warning: 'efifb_set_system' defined but not used [-Wunused-function]
      94 | static int __init efifb_set_system(const struct dmi_system_id *id)
         |                   ^~~~~~~~~~~~~~~~


vim +/efifb_add_links +328 drivers/firmware/efi/sysfb_efi.c

8633ef82f101c0 Javier Martinez Canillas 2021-06-25  320  
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  321  /*
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  322   * If the efifb framebuffer is backed by a PCI graphics controller, we have
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  323   * to ensure that this relation is expressed using a device link when
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  324   * running in DT mode, or the probe order may be reversed, resulting in a
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  325   * resource reservation conflict on the memory window that the efifb
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  326   * framebuffer steals from the PCIe host bridge.
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  327   */
8633ef82f101c0 Javier Martinez Canillas 2021-06-25 @328  static int efifb_add_links(struct fwnode_handle *fwnode)
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  329  {
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  330  	struct device_node *sup_np;
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  331  
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  332  	sup_np = find_pci_overlap_node();
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  333  
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  334  	/*
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  335  	 * If there's no PCI graphics controller backing the efifb, we are
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  336  	 * done here.
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  337  	 */
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  338  	if (!sup_np)
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  339  		return 0;
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  340  
75cde56a5b504d Saravana Kannan          2024-03-04  341  	fwnode_link_add(fwnode, of_fwnode_handle(sup_np), 0);
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  342  	of_node_put(sup_np);
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  343  
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  344  	return 0;
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  345  }
8633ef82f101c0 Javier Martinez Canillas 2021-06-25  346  

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

      reply	other threads:[~2024-10-25  5:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24  8:44 Zeng Heng
2024-10-25  5:03 ` kernel test robot [this message]

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=202410251211.Jze0KkZR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ardb@kernel.org \
    --cc=bobo.shaobowang@huawei.com \
    --cc=bp@suse.de \
    --cc=javierm@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=simona.vetter@ffwll.ch \
    --cc=tzimmermann@suse.de \
    --cc=zengheng4@huawei.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

all inboxes | Powered by JetHome®