linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jagadeesh Banisetti <jagadeesh.banisetti@xilinx.com>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org,
	Michal Simek <monstr@monstr.eu>
Subject: [xilinx-xlnx:master 122/545] drivers/phy/xilinx/xilinx_dpgtquadphy.c:49:17: error: implicit declaration of function 'FIELD_PREP'
Date: Thu, 26 May 2022 00:20:41 +0800	[thread overview]
Message-ID: <202205260053.19oXRWSB-lkp@intel.com> (raw)

Hi Jagadeesh,

FYI, the error/warning still remains.

tree:   https://github.com/Xilinx/linux-xlnx master
head:   8bc116ceb77acddaeffa3daeca192bdfd2aff7c3
commit: a2af060c77e92bff35d0f7176cc5139115ff29b9 [122/545] phy: Add driver for GTQUAD BASE for Displayport
config: um-allyesconfig (https://download.01.org/0day-ci/archive/20220526/202205260053.19oXRWSB-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-1) 11.3.0
reproduce (this is a W=1 build):
        # https://github.com/Xilinx/linux-xlnx/commit/a2af060c77e92bff35d0f7176cc5139115ff29b9
        git remote add xilinx-xlnx https://github.com/Xilinx/linux-xlnx
        git fetch --no-tags xilinx-xlnx master
        git checkout a2af060c77e92bff35d0f7176cc5139115ff29b9
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=um SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   drivers/phy/xilinx/xilinx_dpgtquadphy.c: In function 'xdpgtquad_init':
>> drivers/phy/xilinx/xilinx_dpgtquadphy.c:49:17: error: implicit declaration of function 'FIELD_PREP' [-Werror=implicit-function-declaration]
      49 |         data |= FIELD_PREP(GT_QUAD_BASE_CH1_CLK_DIV_MASK,
         |                 ^~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/FIELD_PREP +49 drivers/phy/xilinx/xilinx_dpgtquadphy.c

    34	
    35	static int xdpgtquad_init(struct phy *phy)
    36	{
    37		struct dpgtquadphy_dev *gtquad = phy_get_drvdata(phy);
    38		u32 data;
    39	
    40		/*
    41		 * Unlocking the NPI space so that GT CH1 divider value can be
    42		 * programmed. This will generate a /20 clk
    43		 */
    44		writel(GT_QUAD_BASE_CTL_VALUE,
    45		       gtquad->base + GT_QUAD_BASE_CTL);
    46	
    47		data = readl(gtquad->base + GT_QUAD_BASE_CH1_CLK_DIV_REG);
    48		data &= ~GT_QUAD_BASE_CH1_CLK_DIV_MASK;
  > 49		data |= FIELD_PREP(GT_QUAD_BASE_CH1_CLK_DIV_MASK,
    50				   GT_QUAD_BASE_CH1_CLK_DIV_VALUE);
    51		writel(data, gtquad->base + GT_QUAD_BASE_CH1_CLK_DIV_REG);
    52	
    53		return 0;
    54	}
    55	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2022-05-25 16:22 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=202205260053.19oXRWSB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jagadeesh.banisetti@xilinx.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=monstr@monstr.eu \
    /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).