From: Jakub Kicinski <kuba@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Simon Horman <simon.horman@corigine.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-kernel@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Shenwei Wang <shenwei.wang@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
linux-stm32@st-md-mailman.stormreply.com,
Zhao Qiang <qiang.zhao@nxp.com>,
Michal Simek <michal.simek@xilinx.com>,
Jose Abreu <joabreu@synopsys.com>,
Clark Wang <xiaoning.wang@nxp.com>,
NXP Linux Team <linux-imx@nxp.com>,
Francois Romieu <romieu@fr.zoreil.com>,
Paolo Abeni <pabeni@redhat.com>, Kalle Valo <kvalo@kernel.org>,
Wolfgang Grandegger <wg@grandegger.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
linuxppc-dev@lists.ozlabs.org, linux-can@vger.kernel.org,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
netdev@vger.k ernel.org, linux-wireless@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Wei Fang <wei.fang@nxp.com>,
Samuel Mendoza-Jonas <sam@mendozajonas.com>,
Shawn Guo <shawnguo@kernel.org>,
Claudiu Beznea <claudiu.beznea@microchip.com>
Subject: Re: [PATCH v2] net: Use of_property_read_bool() for boolean properties
Date: Thu, 16 Mar 2023 17:07:16 -0700 [thread overview]
Message-ID: <20230316170716.7039161d@kernel.org> (raw)
In-Reply-To: <20230314191828.914124-1-robh@kernel.org>
On Tue, 14 Mar 2023 14:18:27 -0500 Rob Herring wrote:
> It is preferred to use typed property access functions (i.e.
> of_property_read_<type> functions) rather than low-level
> of_get_property/of_find_property functions for reading properties.
> Convert reading boolean properties to of_property_read_bool().
>
> Reviewed-by: Simon Horman <simon.horman@corigine.com>
> Acked-by: Marc Kleine-Budde <mkl@pengutronix.de> # for net/can
> Acked-by: Kalle Valo <kvalo@kernel.org>
> Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> Acked-by: Francois Romieu <romieu@fr.zoreil.com>
> Reviewed-by: Wei Fang <wei.fang@nxp.com>
> Signed-off-by: Rob Herring <robh@kernel.org>
Applied, to net(?), thanks!
prev parent reply other threads:[~2023-03-17 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 19:18 [PATCH v2] net: Use of_property_read_bool() for boolean properties Rob Herring
2023-03-16 17:50 ` patchwork-bot+netdevbpf
2023-03-17 0:07 ` Jakub Kicinski [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=20230316170716.7039161d@kernel.org \
--to=kuba@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=claudiu.manoil@nxp.com \
--cc=edumazet@google.com \
--cc=festevam@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=joabreu@synopsys.com \
--cc=kernel@pengutronix.de \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michal.simek@xilinx.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.k \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=qiang.zhao@nxp.com \
--cc=robh@kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=s.hauer@pengutronix.de \
--cc=shenwei.wang@nxp.com \
--cc=simon.horman@corigine.com \
--cc=wg@grandegger.com \
--cc=xiaoning.wang@nxp.com \
/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 NNTP newsgroup(s).