Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   Mark Brown <broonie@kernel.org>
To:     jakobkoschel@gmail.com
Cc:     linux-kernel@vger.kernel.org, bjohannesmeyer@gmail.com,
        rppt@kernel.org, c.giuffrida@vu.nl, h.j.bos@vu.nl,
        linux-spi@vger.kernel.org
In-Reply-To: <20220324072534.63420-1-jakobkoschel@gmail.com>
References: <20220324072534.63420-1-jakobkoschel@gmail.com>
Subject: Re: [PATCH] spi: spidev: replace usage of found with dedicated list iterator variable
Message-Id: <164915114510.276894.6837144397974645999.b4-ty@kernel.org>
Date:   Tue, 05 Apr 2022 10:32:25 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 24 Mar 2022 08:25:34 +0100, Jakob Koschel wrote:
> To move the list iterator variable into the list_for_each_entry_*()
> macro in the future it should be avoided to use the list iterator
> variable after the loop body.
> 
> To *never* use the list iterator variable after the loop it was
> concluded to use a separate iterator variable instead of a
> found boolean [1].
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spidev: replace usage of found with dedicated list iterator variable
      commit: d50d7e91c6e5ccd71f21ba1aec3fef7ee4229fd6

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