Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.32 as permitted sender) client-ip=23.128.96.32;
From:   Mark Brown <broonie@kernel.org>
To:     tmaimon77@gmail.com, tali.perry1@gmail.com, avifishman70@gmail.com,
        joel@jms.id.au,
        "William A. Kennington III" <william@wkennington.com>
Cc:     linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <20230922182812.2728066-1-william@wkennington.com>
References: <20230922182812.2728066-1-william@wkennington.com>
Subject: Re: [PATCH] spi: npcm-fiu: Fix UMA reads when dummy.nbytes == 0
Message-Id: <169626129142.73782.530918104356513259.b4-ty@kernel.org>
Date:   Mon, 02 Oct 2023 16:41:31 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 22 Sep 2023 11:28:12 -0700, William A. Kennington III wrote:
> We don't want to use the value of ilog2(0) as dummy.buswidth is 0 when
> dummy.nbytes is 0. Since we have no dummy bytes, we don't need to
> configure the dummy byte bits per clock register value anyway.
> 
> 

Applied to

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

Thanks!

[1/1] spi: npcm-fiu: Fix UMA reads when dummy.nbytes == 0
      commit: 2ec8b010979036c2fe79a64adb6ecc0bd11e91d1

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