linux-kernel - Re: [PATCH] spi: spi-mtk-nor: initialize spi controller after resume

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

Message-ID: <YlbGaq/o888LNXGk@sirena.org.uk>
Date:   Wed, 13 Apr 2022 13:47:38 +0100
From:   Mark Brown <broonie@...nel.org>
To:     "allen-kh.cheng" <allen-kh.cheng@...iatek.com>
Cc:     ikjn@...omium.org, matthias.bgg@...il.com,
        linux-mediatek@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Project_Global_Chrome_Upstream_Group@...iatek.com,
        linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi: spi-mtk-nor: initialize spi controller after resume

On Wed, Apr 13, 2022 at 11:33:47AM +0800, allen-kh.cheng wrote:

> Sorry, There is one issue I want to correct in commit message.

> "To handle both issues [etc]" should become something like:
> "Solve this issue by reinitializing the registers right after resuming
> the controller"

> Do you mind help me modify commit message? or I can send a new PATCH to
> correst this.

Sorry, there's a merge commit after the patch so I can't easily rebase
(which I don't generally do anyway) - it'll just have to stay the way it
is.  Not the end of the world even if it is unfortunate.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)