From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Linus Walleij <linus.walleij@linaro.org>,
tomeu.vizoso@collabora.com, mgalka@collabora.com,
broonie@kernel.org, matthew.hart@linaro.org,
Scott Branden <scott.branden@broadcom.com>,
khilman@baylibre.com, enric.balletbo@collabora.com,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: Scott Branden <sbranden@broadcom.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Ray Jui <rjui@broadcom.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: next/master boot bisection: next-20191106 on r8a7795-salvator-x
Date: Wed, 6 Nov 2019 22:26:47 +0000 [thread overview]
Message-ID: <e2ba3c23-4b85-f83b-0ba4-dc0db1b8dd0f@collabora.com> (raw)
In-Reply-To: <5dc3460a.1c69fb81.bfae4.adf1@mx.google.com>
On 06/11/2019 22:15, kernelci.org bot wrote:
> +static const struct of_device_id bcm_iproc_gpio_of_match[] __initconst = {
> + { .compatible = "brcm,iproc-gpio-cca" },
> + {}
> +};
> +MODULE_DEVICE_TABLE(of, bcm_iproc_gpio_of_match);
> +
> +static struct platform_driver bcm_iproc_gpio_driver = {
> + .driver = {
> + .name = "iproc-xgs-gpio",
> + .owner = THIS_MODULE,
> + .of_match_table = bcm_iproc_gpio_of_match,
> + },
> + .probe = iproc_gpio_probe,
> + .remove = iproc_gpio_remove,
> +};
There's a fix for this which Mark sent yesterday[1] and should
have now been applied, by removing __initconst for the
of_device_id table. So this regression should not be present in
the next linux-next tag.
Guillaume
[1] https://www.spinics.net/lists/arm-kernel/msg766621.html
next prev parent reply other threads:[~2019-11-06 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 22:15 kernelci.org bot
2019-11-06 22:26 ` Guillaume Tucker [this message]
2019-11-07 8:04 ` Linus Walleij
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=e2ba3c23-4b85-f83b-0ba4-dc0db1b8dd0f@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=enric.balletbo@collabora.com \
--cc=khilman@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.hart@linaro.org \
--cc=mgalka@collabora.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=scott.branden@broadcom.com \
--cc=tomeu.vizoso@collabora.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®