linux-kernel - Re: [PATCH v2] spi: dw-bt1: Fix undefined devm_mux_control

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]

Date:   Fri, 27 Nov 2020 16:20:29 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Serge Semin <Sergey.Semin@...kalelectronics.ru>,
        Ramil Zaripov <Ramil.Zaripov@...kalelectronics.ru>
Cc:     linux-spi@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>,
        kernel test robot <lkp@...el.com>,
        Serge Semin <fancer.lancer@...il.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] spi: dw-bt1: Fix undefined devm_mux_control_get symbol

On Fri, 27 Nov 2020 17:46:11 +0300, Serge Semin wrote:
> I mistakenly added the select attributes to the SPI_DW_BT1_DIRMAP config
> instead of having them defined in SPI_DW_BT1. If the kernel doesn't have
> the MULTIPLEXER and MUX_MMIO configs manually enabled and the
> SPI_DW_BT1_DIRMAP config hasn't been selected, Baikal-T1 SPI device will
> always fail to be probed by the driver. Fix that and the error reported by
> the test robot:
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: dw-bt1: Fix undefined devm_mux_control_get symbol
      commit: 7218838109fef61cdec988ff728e902d434c9cc5

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