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:     joel.peshkin@broadcom.com, dregan@mail.com, jonas.gorski@gmail.com,
        dan.beygelman@broadcom.com, f.fainelli@gmail.com,
        anand.gore@broadcom.com, kursad.oney@broadcom.com,
        tomer.yacoby@broadcom.com, kernel test robot <lkp@intel.com>,
        linux-kernel@vger.kernel.org
In-Reply-To: <20230307012004.414502-1-william.zhang@broadcom.com>
References: <20230307012004.414502-1-william.zhang@broadcom.com>
Subject: Re: [PATCH] spi: Fix cocci warnings
Message-Id: <167820770115.97370.5301180632243342942.b4-ty@kernel.org>
Date:   Tue, 07 Mar 2023 16:48:21 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Mon, 06 Mar 2023 17:20:04 -0800, William Zhang wrote:
> cocci reported warning: !A || A && B is equivalent to !A || B. This fix
> simplified the condition check to !A || B.
> 
> Fixes: 76a85704cb91 ("spi: spi-mem: Allow controller supporting mem_ops without exec_op")
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://lore.kernel.org/oe-kbuild-all/202303010051.HrHWSr9y-lkp@intel.com/
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: Fix cocci warnings
      commit: 20064c47f63e995216e0dfb0a6ea37b653ed534c

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