linux-kernel - Re: [PATCH 1/1] spi: altera: Change to dynamic allocation of spi id

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: <163472931597.2896731.8898998554270520843.b4-ty@kernel.org>
Date:   Wed, 20 Oct 2021 12:28:35 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Russ Weight <russell.h.weight@...el.com>,
        linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     Mark Brown <broonie@...nel.org>, yilun.xu@...el.com,
        hao.wu@...el.com, trix@...hat.com, matthew.gerlach@...el.com,
        lgoncalv@...hat.com
Subject: Re: [PATCH 1/1] spi: altera: Change to dynamic allocation of spi id

On Mon, 18 Oct 2021 17:24:01 -0700, Russ Weight wrote:
> The spi-altera driver has two flavors: platform and dfl. I'm seeing
> a case where I have both device types in the same machine, and they
> are conflicting on the SPI ID:
> 
> ... kernel: couldn't get idr
> ... kernel: WARNING: CPU: 28 PID: 912 at drivers/spi/spi.c:2920 spi_register_controller.cold+0x84/0xc0a
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: altera: Change to dynamic allocation of spi id
      commit: f09f6dfef8ce7b70a240cf83811e2b1909c3e47b

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