linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Breathitt Gray <william.gray@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the gpio-brgl tree
Date: Wed, 22 Mar 2023 15:50:00 -0400	[thread overview]
Message-ID: <ZBtb6ML7FmMZ6uQ3@fedora> (raw)
In-Reply-To: <20230323122913.4f0410b8@canb.auug.org.au>

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

On Thu, Mar 23, 2023 at 12:29:13PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the gpio-brgl tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/gpio/gpio-pci-idio-16.c:32:30: error: field 'state' has incomplete type
>    32 |         struct idio_16_state state;
>       |                              ^~~~~
> drivers/gpio/gpio-pci-idio-16.c: In function 'idio_16_gpio_get_direction':
> drivers/gpio/gpio-pci-idio-16.c:39:13: error: implicit declaration of function 'idio_16_get_direction'; did you mean 'idio_16_gpio_get_direction'? [-Werror=implicit-function-declaration]
>    39 |         if (idio_16_get_direction(offset))
>       |             ^~~~~~~~~~~~~~~~~~~~~
>       |             idio_16_gpio_get_direction
> drivers/gpio/gpio-pci-idio-16.c: In function 'idio_16_gpio_get':
> drivers/gpio/gpio-pci-idio-16.c:62:16: error: implicit declaration of function 'idio_16_get'; did you mean 'idio_16_gpio_get'? [-Werror=implicit-function-declaration]
>    62 |         return idio_16_get(idio16gpio->reg, &idio16gpio->state, offset);
>       |                ^~~~~~~~~~~
>       |                idio_16_gpio_get
> drivers/gpio/gpio-pci-idio-16.c: In function 'idio_16_gpio_get_multiple':
> drivers/gpio/gpio-pci-idio-16.c:70:9: error: implicit declaration of function 'idio_16_get_multiple'; did you mean 'idio_16_gpio_get_multiple'? [-Werror=implicit-function-declaration]
>    70 |         idio_16_get_multiple(idio16gpio->reg, &idio16gpio->state, mask, bits);
>       |         ^~~~~~~~~~~~~~~~~~~~
>       |         idio_16_gpio_get_multiple
> drivers/gpio/gpio-pci-idio-16.c: In function 'idio_16_gpio_set':
> drivers/gpio/gpio-pci-idio-16.c:79:9: error: implicit declaration of function 'idio_16_set'; did you mean 'idio_16_gpio_set'? [-Werror=implicit-function-declaration]
>    79 |         idio_16_set(idio16gpio->reg, &idio16gpio->state, offset, value);
>       |         ^~~~~~~~~~~
>       |         idio_16_gpio_set
> drivers/gpio/gpio-pci-idio-16.c: In function 'idio_16_gpio_set_multiple':
> drivers/gpio/gpio-pci-idio-16.c:87:9: error: implicit declaration of function 'idio_16_set_multiple'; did you mean 'idio_16_gpio_set_multiple'? [-Werror=implicit-function-declaration]
>    87 |         idio_16_set_multiple(idio16gpio->reg, &idio16gpio->state, mask, bits);
>       |         ^~~~~~~~~~~~~~~~~~~~
>       |         idio_16_gpio_set_multiple
> drivers/gpio/gpio-pci-idio-16.c: In function 'idio_16_irq_mask':
> drivers/gpio/gpio-pci-idio-16.c:106:45: error: invalid use of undefined type 'struct idio_16'
>   106 |                 iowrite8(0, &idio16gpio->reg->irq_ctl);
>       |                                             ^~
> drivers/gpio/gpio-pci-idio-16.c: In function 'idio_16_irq_unmask':
> drivers/gpio/gpio-pci-idio-16.c:129:41: error: invalid use of undefined type 'struct idio_16'
>   129 |                 ioread8(&idio16gpio->reg->irq_ctl);
>       |                                         ^~
> drivers/gpio/gpio-pci-idio-16.c: In function 'idio_16_irq_handler':
> drivers/gpio/gpio-pci-idio-16.c:164:46: error: invalid use of undefined type 'struct idio_16'
>   164 |         irq_status = ioread8(&idio16gpio->reg->irq_status);
>       |                                              ^~
> drivers/gpio/gpio-pci-idio-16.c:178:37: error: invalid use of undefined type 'struct idio_16'
>   178 |         iowrite8(0, &idio16gpio->reg->in0_7);
>       |                                     ^~
> drivers/gpio/gpio-pci-idio-16.c: In function 'idio_16_irq_init_hw':
> drivers/gpio/gpio-pci-idio-16.c:198:37: error: invalid use of undefined type 'struct idio_16'
>   198 |         iowrite8(0, &idio16gpio->reg->irq_ctl);
>       |                                     ^~
> drivers/gpio/gpio-pci-idio-16.c:199:37: error: invalid use of undefined type 'struct idio_16'
>   199 |         iowrite8(0, &idio16gpio->reg->in0_7);
>       |                                     ^~
> drivers/gpio/gpio-pci-idio-16.c: In function 'idio_16_probe':
> drivers/gpio/gpio-pci-idio-16.c:232:37: error: invalid use of undefined type 'struct idio_16'
>   232 |         iowrite8(0, &idio16gpio->reg->filter_ctl);
>       |                                     ^~
> drivers/gpio/gpio-pci-idio-16.c:248:9: error: implicit declaration of function 'idio_16_state_init'; did you mean 'file_ra_state_init'? [-Werror=implicit-function-declaration]
>   248 |         idio_16_state_init(&idio16gpio->state);
>       |         ^~~~~~~~~~~~~~~~~~
>       |         file_ra_state_init
> drivers/gpio/gpio-pci-idio-16.c: In function 'idio_16_gpio_get':
> drivers/gpio/gpio-pci-idio-16.c:63:1: error: control reaches end of non-void function [-Werror=return-type]
>    63 | }
>       | ^
> 
> Caused by commit
> 
>   473b79057bbd ("gpio: idio-16: Remove unused legacy interface")
> 
> I have used the gpio-brgl tree from next-20230322 for today.
> 
> -- 
> Cheers,
> Stephen Rothwell

Commit 473b79057bbd shouldn't be merged until all of the IDIO-16 legacy
interface is first removed.

Bart, would you revert all of the "Migrate IDIO-16 GPIO drivers to
regmap API" patches [0]? That patchset needs to be revised anyway to
prevent conflicts with the handle_mask_sync() API change [1]; I'll
submit a v3 later this week that resolves the incompatibilies and
rebase on the latest gpio/for-next.

William Breathitt Gray

[0] https://lore.kernel.org/all/cover.1677515341.git.william.gray@linaro.org/
[1] https://lore.kernel.org/all/cover.1679323449.git.william.gray@linaro.org/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-03-23  1:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  1:29 linux-next: build failure after merge of the gpio-brgl tree Stephen Rothwell
2023-03-22 19:50 ` William Breathitt Gray [this message]
2023-03-23 13:32   ` Bartosz Golaszewski
  -- strict thread matches above, loose matches on Subject: below --
2024-02-23  3:33 Stephen Rothwell
2024-02-23  7:51 ` Bartosz Golaszewski
2024-02-23 12:29   ` Andy Shevchenko
2024-02-25  1:58   ` Stephen Rothwell
2024-02-26 19:07     ` Bartosz Golaszewski
2023-10-13  4:14 Stephen Rothwell
2023-10-13  6:44 ` Bartosz Golaszewski
2021-12-20  5:51 Stephen Rothwell
2021-12-20 12:46 ` Andy Shevchenko
2021-12-13 20:31 broonie
2021-12-14  3:12 ` Florian Fainelli
2021-12-17  6:17   ` Stephen Rothwell
2021-12-17  9:14     ` Bartosz Golaszewski
2021-11-15 23:51 Stephen Rothwell
2021-11-17 21:29 ` Rob Herring
2021-11-18  0:29 ` Stephen Rothwell
2021-11-23  2:04   ` Stephen Rothwell
2021-12-02  3:16     ` Stephen Rothwell
2021-02-18  6:54 Stephen Rothwell

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=ZBtb6ML7FmMZ6uQ3@fedora \
    --to=william.gray@linaro.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).