All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [freescale-fslc:5.15-2.2.x-imx 3225/29983] drivers/gpio/gpio-scu.c:99:11: error: 'struct gpio_chip' has no member named 'of_node'
Date: Mon, 29 Apr 2024 17:47:54 +0800	[thread overview]
Message-ID: <202404291717.Sp3gkRKd-lkp@intel.com> (raw)

Hi Shenwei,

FYI, the error/warning still remains.

tree:   https://github.com/Freescale/linux-fslc 5.15-2.2.x-imx
head:   5134e031114e613cb04858e248af5e65fe1e112f
commit: cdb7bf80f99743df8c3375d3191d3b96661c4b65 [3225/29983] MLK-25166-1 gpio: gpio-scu: gpio driver over scu fw misc api
config: parisc-randconfig-001-20240429 (https://download.01.org/0day-ci/archive/20240429/202404291717.Sp3gkRKd-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240429/202404291717.Sp3gkRKd-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/202404291717.Sp3gkRKd-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/gpio/gpio-scu.c: In function 'imx_scu_gpio_probe':
>> drivers/gpio/gpio-scu.c:99:11: error: 'struct gpio_chip' has no member named 'of_node'
      99 |         gc->of_node = np;
         |           ^~


vim +99 drivers/gpio/gpio-scu.c

    80	
    81	static int imx_scu_gpio_probe(struct platform_device *pdev)
    82	{
    83		struct device *dev = &pdev->dev;
    84		struct device_node *np = dev->of_node;
    85		struct imxscfw *port;
    86		struct gpio_chip *gc;
    87		int ret;
    88	
    89		port = devm_kzalloc(&pdev->dev, sizeof(*port), GFP_KERNEL);
    90		if (!port)
    91			return -ENOMEM;
    92	
    93		ret = imx_scu_get_handle(&port->handle);
    94		if (ret)
    95			return ret;
    96	
    97		mutex_init(&port->lock);
    98		gc = &port->chip;
  > 99		gc->of_node = np;
   100		gc->parent = dev;
   101		gc->label = "imx-scu-gpio";
   102		gc->ngpio = PIN_NUMBER;
   103		gc->base = of_alias_get_id(np, "gpio") * 32;
   104	
   105		gc->get = imxscfw_get;
   106		gc->set = imxscfw_set;
   107	
   108		platform_set_drvdata(pdev, port);
   109	
   110		ret = devm_gpiochip_add_data(dev, gc, port);
   111	
   112		return ret;
   113	}
   114	

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

                 reply	other threads:[~2024-04-29  9:48 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=202404291717.Sp3gkRKd-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=otavio@ossystems.com.br \
    /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.