Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Mark Brown <broonie@kernel.org>
To:     linux-spi@vger.kernel.org,
        Yang Yingliang <yangyingliang@huawei.com>,
        linux-kernel@vger.kernel.org
Cc:     Mark Brown <broonie@kernel.org>, zhengxunli@mxic.com.tw
Subject: Re: [PATCH -next] spi: mxic: add missing braces
Date:   Fri, 13 Aug 2021 18:25:59 +0100
Message-Id: <162887483202.19992.2868965211824266055.b4-ty@kernel.org>
In-Reply-To: <20210810142405.2221540-1-yangyingliang@huawei.com>
References: <20210810142405.2221540-1-yangyingliang@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 10 Aug 2021 22:24:05 +0800, Yang Yingliang wrote:
> Fix the following waring:
> 
> drivers/spi/spi-mxic.c: In function ‘mxic_spi_mem_exec_op’:
> drivers/spi/spi-mxic.c:401:3: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
>    if (op->data.dir == SPI_MEM_DATA_IN)
>    ^~
> drivers/spi/spi-mxic.c:403:4: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
>     if (op->data.dtr)
>     ^~
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: mxic: add missing braces
      commit: aca196842a9729a198af57c417725c3ac9ca05db

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