linux-kernel - Re: [PATCH v2] spi: mediatek: skip delays if they are 0

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: <163313375302.13893.4068868673523917902.b4-ty@kernel.org>
Date:   Sat,  2 Oct 2021 01:16:22 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Dafna Hirschfeld <dafna.hirschfeld@...labora.com>
Cc:     Mark Brown <broonie@...nel.org>, wsd_upstream@...iatek.com,
        linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
        linux-spi@...r.kernel.org, dafna3@...il.com,
        Matthias Brugger <matthias.bgg@...il.com>,
        kernel@...labora.com, enric.balletbo@...labora.com,
        Mason Zhang <Mason.Zhang@...iatek.com>,
        Laxman Dewangan <ldewangan@...dia.com>,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] spi: mediatek: skip delays if they are 0

On Fri, 1 Oct 2021 17:21:53 +0200, Dafna Hirschfeld wrote:
> In the function 'mtk_spi_set_hw_cs_timing'
> the 'setup', 'hold' and 'inactive' delays are configured.
> In case those values are 0 it causes errors on mt8173:
> 
> cros-ec-i2c-tunnel 1100a000.spi:ec@0:i2c-tunnel0:
> 	Error transferring EC i2c message -71
> cros-ec-spi spi0.0: EC failed to respond in time.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: mediatek: skip delays if they are 0
      commit: 3672bb820f3292b6f035469f863c020317a3dd28

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark