linux-kernel - Re: [PATCH] spi: fsl: add missing _

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:   Wed, 01 Jul 2020 23:24:43 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Luc Van Oostenryck <luc.vanoostenryck@...il.com>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] spi: fsl: add missing __iomem annotation

On Mon, 22 Jun 2020 18:26:11 +0200, Luc Van Oostenryck wrote:
> The field mspi->reg_base is annotated as an __iomem pointer. Good.
> 
> However, this field is often assigned to a temporary variable:
> before being used. For example:
> 	struct fsl_spi_reg *reg_base = mspi->reg_base;
> 
> But this variable is missing the __iomem annotation.
> So, add the missing __iomem and make sparse & the bot happier.

Applied to

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

Thanks!

[1/1] spi: fsl: add missing __iomem annotation
      commit: dd67de8c3b421376b4b6dac14263763aa75535fc

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