linux-kernel - Re: [PATCH v1 0/3] spi: npcm-fiu: add Arbel NPCM8XX 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: <165834042733.589042.2864906716831607368.b4-ty@kernel.org>
Date:   Wed, 20 Jul 2022 19:07:07 +0100
From:   Mark Brown <broonie@...nel.org>
To:     benjaminfair@...gle.com, tali.perry1@...il.com, robh+dt@...nel.org,
        krzysztof.kozlowski+dt@...aro.org, venture@...gle.com,
        avifishman70@...il.com, tmaimon77@...il.com, yuenn@...gle.com,
        joel@....id.au
Cc:     devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        openbmc@...ts.ozlabs.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH v1 0/3] spi: npcm-fiu: add Arbel NPCM8XX support

On Mon, 18 Jul 2022 11:11:43 +0300, Tomer Maimon wrote:
> This patch set adds Arbel NPCM8XX Flash Interface Unit (FIU) support to FIU NPCM
> driver and modify direct read dummy configuration.
> 
> NPCM8XX FIU supports four controllers.
> 
> The NPCM FIU driver tested on NPCM845 evaluation board.
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: npcm-fiu: Modify direct read dummy configuration
      commit: 7c3193f7890a03fc1b5b979f3f8dc8750ef47b13
[2/3] dt-binding: spi: Add npcm845 compatible to npcm-fiu document
      commit: d50fef8ae939c2b50431fe6a11457e7ff85aea55
[3/3] spi: npcm-fiu: Add NPCM8XX support
      commit: 650b014facca5238e25399f28da1e59747bddb99

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