linux-kernel - Aw: Re: [BUG] [PATCH v5 02/10] mfd: mt6397: extract irq related code from core driver

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <trinity-a57f08bb-e30e-4e74-911c-c40e335d00da-1566580580817@3c-app-gmx-bs75>
Date:   Fri, 23 Aug 2019 19:16:20 +0200
From:   "Frank Wunderlich" <frank-w@...lic-files.de>
To:     "Matthias Brugger" <matthias.bgg@...il.com>
Cc:     linux-mediatek@...ts.infradead.org,
        "Hsin-Hsiung Wang" <hsin-hsiung.wang@...iatek.com>,
        "Mark Rutland" <mark.rutland@....com>,
        "Alessandro Zummo" <a.zummo@...ertech.it>,
        "Alexandre Belloni" <alexandre.belloni@...tlin.com>,
        srv_heupstream@...iatek.com, devicetree@...r.kernel.org,
        "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
        "Sean Wang" <sean.wang@...iatek.com>,
        "Liam Girdwood" <lgirdwood@...il.com>,
        "Rob Herring" <robh+dt@...nel.org>, linux-kernel@...r.kernel.org,
        "Richard Fontana" <rfontana@...hat.com>,
        "Mark Brown" <broonie@...nel.org>,
        linux-arm-kernel@...ts.infradead.org,
        "René van Dorst" <opensource@...rst.com>,
        "Thomas Gleixner" <tglx@...utronix.de>,
        "Eddie Huang" <eddie.huang@...iatek.com>,
        "Lee Jones" <lee.jones@...aro.org>,
        "Kate Stewart" <kstewart@...uxfoundation.org>,
        linux-rtc@...r.kernel.org
Subject: Aw: Re: [BUG] [PATCH v5 02/10] mfd: mt6397: extract irq related
 code from core driver

> Gesendet: Freitag, 23. August 2019 um 17:42 Uhr
> Von: "Matthias Brugger" <matthias.bgg@...il.com>

> I suppose that's because 3/10 has code that should be in 2/10 and for some
> reason 3/10 was not pushed for linux-next inclusion. Although it has the same
> Acked-for-mfd-by tag.
>
> @Frank, can you test if adding 3/10 to your code base fixes the issue?

adding part 3 [1] seems to fix the issue too

[    4.960051] mt6323-regulator mt6323-regulator: Chip ID = 0x2023

thanks

[1] https://patchwork.kernel.org/patch/11110509/