linux-kernel - Re: [PATCH v1 0/2] Remove Intel Thunder Bay SOC support

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: <170248512843.27334.1958241029702729417.b4-ty@kernel.org>
Date:   Wed, 13 Dec 2023 16:32:08 +0000
From:   Mark Brown <broonie@...nel.org>
To:     fancer.lancer@...il.com, robh+dt@...nel.org,
        linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        nandhini.srikandan@...el.com
Cc:     devicetree@...r.kernel.org, mgross@...ux.intel.com,
        kris.pan@...el.com, kenchappa.demakkanavar@...el.com,
        furong.zhou@...el.com, mallikarjunappa.sangannavar@...el.com,
        mahesh.r.vaidya@...el.com
Subject: Re: [PATCH v1 0/2] Remove Intel Thunder Bay SOC support

On Wed, 13 Dec 2023 14:08:34 +0800, nandhini.srikandan@...el.com wrote:
> This patch set removes Intel Thunder Bay specific code as the product
> got cancelled and there are no end customers.
> 
> Patch 1: Remove Intel Thunder Bay spi dw binding specific code.
> Patch 2: Remove Intel Thunder Bay spi dw binding Documentation.
> 
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: dw: Remove Intel Thunder Bay SOC support
      commit: e1fca6957f1966cb6e75cdc354f4bcaed230a454
[2/2] spi: dw: Remove Intel Thunder Bay SOC support
      commit: e1fca6957f1966cb6e75cdc354f4bcaed230a454

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