From:   Mark Brown <broonie@kernel.org>
To:     Linux SPI List <linux-spi@vger.kernel.org>,
        Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
        William Zhang <william.zhang@broadcom.com>
Cc:     dan.beygelman@broadcom.com, f.fainelli@gmail.com,
        tomer.yacoby@broadcom.com, kursad.oney@broadcom.com,
        dregan@mail.com, anand.gore@broadcom.com, jonas.gorski@gmail.com,
        joel.peshkin@broadcom.com, kernel test robot <lkp@intel.com>,
        =?utf-8?q?Rafa=C5=82_Mi=C5=82ecki?= <rafal@milecki.pl>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
In-Reply-To: <20230211032759.72967-1-william.zhang@broadcom.com>
References: <20230211032759.72967-1-william.zhang@broadcom.com>
Subject: Re: [PATCH] spi: bcm63xx-hsspi: bcmbca-hsspi: fix _be16 type usage
Message-Id: <167629819904.2707397.9836890482883162209.b4-ty@kernel.org>
Date:   Mon, 13 Feb 2023 14:23:19 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 10 Feb 2023 19:27:59 -0800, William Zhang wrote:
> sparse tool report warnings: drivers/spi/spi-bcm63xx-hsspi.c:197:31:
> sparse: sparse: cast from restricted __be16.
> 
> The controller requires big endian 16 bit data. Define an intermediate
> u16 value and use __be16 piointer dereferncing for the data to avoid
> directly casting to u16 and sparse warning.
> 
> [...]

Applied to

   broonie/spi.git for-next

Thanks!

[1/1] spi: bcm63xx-hsspi: bcmbca-hsspi: fix _be16 type usage
      commit: 2cca486cad4bf51da57cdad150697476a702ab69

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