linux-kernel - Re: next/master boot bisection: next-20191106 on r8a7795-salvator-x

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACRpkdYA9TgBWb2TQzSVtV1CWy6ZOXA1=8NjSg5bksrNM1C=NA@mail.gmail.com>
Date:   Thu, 7 Nov 2019 09:04:08 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Guillaume Tucker <guillaume.tucker@...labora.com>
Cc:     Tomeu Vizoso <tomeu.vizoso@...labora.com>, mgalka@...labora.com,
        Mark Brown <broonie@...nel.org>,
        Matt Hart <matthew.hart@...aro.org>,
        Scott Branden <scott.branden@...adcom.com>,
        Kevin Hilman <khilman@...libre.com>,
        Enric Balletbo i Serra <enric.balletbo@...labora.com>,
        Chris Packham <chris.packham@...iedtelesis.co.nz>,
        Scott Branden <sbranden@...adcom.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        bcm-kernel-feedback-list <bcm-kernel-feedback-list@...adcom.com>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        Ray Jui <rjui@...adcom.com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: next/master boot bisection: next-20191106 on r8a7795-salvator-x

On Wed, Nov 6, 2019 at 11:27 PM Guillaume Tucker
<guillaume.tucker@...labora.com> wrote:
> 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.

Confirmed, I pushed a new for-next branch with this fix in it.

Yours,
Linus Walleij