All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: kernel test robot <lkp@intel.com>, lewis.hanly@microchip.com
Cc: linux-gpio@vger.kernel.org, linux-riscv@lists.infradead.org,
	palmer@dabbelt.com, kbuild-all@lists.01.org,
	paul.walmsley@sifive.com, conor.dooley@microchip.com,
	daire.mcnamara@microchip.com
Subject: Re: [PATCH 1/1] gpio: mpfs - add polarfire soc gpio support
Date: Thu, 07 Jul 2022 14:03:04 +0100	[thread overview]
Message-ID: <87wncpkrcn.wl-maz@kernel.org> (raw)
In-Reply-To: <202207071219.0Jw0owWG-lkp@intel.com>

On Thu, 07 Jul 2022 05:46:44 +0100,
kernel test robot <lkp@intel.com> wrote:
> 
> Hi,
> 
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on brgl/gpio/for-next]
> [also build test ERROR on linus/master v5.19-rc5 next-20220706]
> [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/lewis-hanly-microchip-com/Add-Polarfire-SoC-GPIO-support/20220705-220421
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
> config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220707/202207071219.0Jw0owWG-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
> reproduce (this is a W=1 build):
>         # https://github.com/intel-lab-lkp/linux/commit/f1c1cf42734c00cf02babb6220f8b68a62e86d0e
>         git remote add linux-review https://github.com/intel-lab-lkp/linux
>         git fetch --no-tags linux-review lewis-hanly-microchip-com/Add-Polarfire-SoC-GPIO-support/20220705-220421
>         git checkout f1c1cf42734c00cf02babb6220f8b68a62e86d0e
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/
> 
> 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/gpio/gpio-mpfs.c: In function 'mpfs_gpio_probe':
> >> drivers/gpio/gpio-mpfs.c:290:20: error: 'struct irq_chip' has no member named 'parent_device'
>      290 |         irq_c->chip->parent_device = dev;
>          |                    ^~
> >> drivers/gpio/gpio-mpfs.c:310:23: error: implicit declaration of function 'devm_request_irq'; did you mean 'can_request_irq'? [-Werror=implicit-function-declaration]
>      310 |                 ret = devm_request_irq(&pdev->dev, irq,

I missed this in my initial eyeballing of this patch. This should
implement a chained interrupt flow, and not request the mux interrupt
directly. That's yet another level of brokenness in this driver.

	M.

-- 
Without deviation from the norm, progress is not possible.

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: kernel test robot <lkp@intel.com>, lewis.hanly@microchip.com
Cc: linux-gpio@vger.kernel.org, linux-riscv@lists.infradead.org,
	palmer@dabbelt.com, kbuild-all@lists.01.org,
	paul.walmsley@sifive.com, conor.dooley@microchip.com,
	daire.mcnamara@microchip.com
Subject: Re: [PATCH 1/1] gpio: mpfs - add polarfire soc gpio support
Date: Thu, 07 Jul 2022 14:03:04 +0100	[thread overview]
Message-ID: <87wncpkrcn.wl-maz@kernel.org> (raw)
In-Reply-To: <202207071219.0Jw0owWG-lkp@intel.com>

On Thu, 07 Jul 2022 05:46:44 +0100,
kernel test robot <lkp@intel.com> wrote:
> 
> Hi,
> 
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on brgl/gpio/for-next]
> [also build test ERROR on linus/master v5.19-rc5 next-20220706]
> [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/lewis-hanly-microchip-com/Add-Polarfire-SoC-GPIO-support/20220705-220421
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
> config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220707/202207071219.0Jw0owWG-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
> reproduce (this is a W=1 build):
>         # https://github.com/intel-lab-lkp/linux/commit/f1c1cf42734c00cf02babb6220f8b68a62e86d0e
>         git remote add linux-review https://github.com/intel-lab-lkp/linux
>         git fetch --no-tags linux-review lewis-hanly-microchip-com/Add-Polarfire-SoC-GPIO-support/20220705-220421
>         git checkout f1c1cf42734c00cf02babb6220f8b68a62e86d0e
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/
> 
> 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/gpio/gpio-mpfs.c: In function 'mpfs_gpio_probe':
> >> drivers/gpio/gpio-mpfs.c:290:20: error: 'struct irq_chip' has no member named 'parent_device'
>      290 |         irq_c->chip->parent_device = dev;
>          |                    ^~
> >> drivers/gpio/gpio-mpfs.c:310:23: error: implicit declaration of function 'devm_request_irq'; did you mean 'can_request_irq'? [-Werror=implicit-function-declaration]
>      310 |                 ret = devm_request_irq(&pdev->dev, irq,

I missed this in my initial eyeballing of this patch. This should
implement a chained interrupt flow, and not request the mux interrupt
directly. That's yet another level of brokenness in this driver.

	M.

-- 
Without deviation from the norm, progress is not possible.

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

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/1] gpio: mpfs - add polarfire soc gpio support
Date: Thu, 07 Jul 2022 14:03:04 +0100	[thread overview]
Message-ID: <87wncpkrcn.wl-maz@kernel.org> (raw)
In-Reply-To: <202207071219.0Jw0owWG-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]

On Thu, 07 Jul 2022 05:46:44 +0100,
kernel test robot <lkp@intel.com> wrote:
> 
> Hi,
> 
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on brgl/gpio/for-next]
> [also build test ERROR on linus/master v5.19-rc5 next-20220706]
> [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/lewis-hanly-microchip-com/Add-Polarfire-SoC-GPIO-support/20220705-220421
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
> config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20220707/202207071219.0Jw0owWG-lkp(a)intel.com/config)
> compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
> reproduce (this is a W=1 build):
>         # https://github.com/intel-lab-lkp/linux/commit/f1c1cf42734c00cf02babb6220f8b68a62e86d0e
>         git remote add linux-review https://github.com/intel-lab-lkp/linux
>         git fetch --no-tags linux-review lewis-hanly-microchip-com/Add-Polarfire-SoC-GPIO-support/20220705-220421
>         git checkout f1c1cf42734c00cf02babb6220f8b68a62e86d0e
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/
> 
> 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/gpio/gpio-mpfs.c: In function 'mpfs_gpio_probe':
> >> drivers/gpio/gpio-mpfs.c:290:20: error: 'struct irq_chip' has no member named 'parent_device'
>      290 |         irq_c->chip->parent_device = dev;
>          |                    ^~
> >> drivers/gpio/gpio-mpfs.c:310:23: error: implicit declaration of function 'devm_request_irq'; did you mean 'can_request_irq'? [-Werror=implicit-function-declaration]
>      310 |                 ret = devm_request_irq(&pdev->dev, irq,

I missed this in my initial eyeballing of this patch. This should
implement a chained interrupt flow, and not request the mux interrupt
directly. That's yet another level of brokenness in this driver.

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2022-07-07 13:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 13:49 [PATCH 0/1] Add Polarfire SoC GPIO support lewis.hanly
2022-07-05 13:49 ` lewis.hanly
2022-07-05 13:49 ` [PATCH 1/1] gpio: mpfs - add polarfire soc gpio support lewis.hanly
2022-07-05 13:49   ` lewis.hanly
2022-07-05 15:17   ` Conor.Dooley
2022-07-05 15:17     ` Conor.Dooley
2022-07-06  5:34     ` Lewis.Hanly
2022-07-06  5:34       ` Lewis.Hanly
2022-07-06  6:50   ` Marc Zyngier
2022-07-06  6:50     ` Marc Zyngier
2022-07-06 10:03   ` Ben Dooks
2022-07-06 10:03     ` Ben Dooks
2022-07-11 12:26     ` Lewis.Hanly
2022-07-11 12:26       ` Lewis.Hanly
2022-07-07  4:46   ` kernel test robot
2022-07-07  4:46     ` kernel test robot
2022-07-07 13:03     ` Marc Zyngier [this message]
2022-07-07 13:03       ` Marc Zyngier
2022-07-07 13:03       ` Marc Zyngier

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=87wncpkrcn.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=kbuild-all@lists.01.org \
    --cc=lewis.hanly@microchip.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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 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.