From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Kousik Sanagavarapu <five231003@gmail.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Julia Lawall <julia.lawall@inria.fr>
Subject: Re: [PATCH] spi: cadence-xspi: use for_each_available_child_of_node_scoped()
Date: Wed, 10 Apr 2024 20:37:28 +0100 [thread overview]
Message-ID: <171277784885.58234.7125195961063638133.b4-ty@kernel.org> (raw)
In-Reply-To: <20240410130205.179069-1-five231003@gmail.com>
On Wed, 10 Apr 2024 18:31:16 +0530, Kousik Sanagavarapu wrote:
> Refactor code for "is the node's child available?" check by using the
> corresponding macro instead, which reads more clearly.
>
> While at it, use scope-based cleanup instead of manual of_node_put()
> calls when getting platform data through cdns_xspi_of_get_plat_data().
>
> This removes the unnecessary "node_child" declaration out of the loop's
> scope and auto cleans up "node_child" when it goes out of scope, even
> when we return early due to error.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: cadence-xspi: use for_each_available_child_of_node_scoped()
commit: b0f3e56938f8cc8c4d606846270b879650ae7741
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
prev parent reply other threads:[~2024-04-10 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 13:01 [PATCH] spi: cadence-xspi: use for_each_available_child_of_node_scoped() Kousik Sanagavarapu
2024-04-10 19:37 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171277784885.58234.7125195961063638133.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=five231003@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).