devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	linux-kernel@vger.kernel.org,
	Frank Rowand <frowand.list@gmail.com>
Subject: Re: [PATCH v3 2/3] of: property: define of_property_read_u{8,16,32,64}_array() unconditionally
Date: Thu, 20 Jan 2022 11:31:07 -0600	[thread overview]
Message-ID: <YemcW0c8U5mtucP+@robh.at.kernel.org> (raw)
In-Reply-To: <20220118173504.2867523-3-michael@walle.cc>

On Tue, 18 Jan 2022 18:35:03 +0100, Michael Walle wrote:
> We can get rid of all the empty stubs because all these functions call
> of_property_read_variable_u{8,16,32,64}_array() which already have an
> empty stub if CONFIG_OF is not defined.
> 
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> changes since v2:
>  - none
> 
> changes since v1:
>  - new patch
> 
>  include/linux/of.h | 274 ++++++++++++++++++++-------------------------
>  1 file changed, 124 insertions(+), 150 deletions(-)
> 

Applied, thanks!

  reply	other threads:[~2022-01-20 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 17:35 [PATCH v3 0/3] of: base: of_parse_phandle() cleanup and new variant Michael Walle
2022-01-18 17:35 ` [PATCH v3 1/3] of: base: make small of_parse_phandle() variants static inline Michael Walle
2022-01-20 17:30   ` Rob Herring
2022-01-18 17:35 ` [PATCH v3 2/3] of: property: define of_property_read_u{8,16,32,64}_array() unconditionally Michael Walle
2022-01-20 17:31   ` Rob Herring [this message]
2022-01-18 17:35 ` [PATCH v3 3/3] of: base: add of_parse_phandle_with_optional_args() Michael Walle
2022-01-24 14:23   ` Rob Herring

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=YemcW0c8U5mtucP+@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=robh+dt@kernel.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 NNTP newsgroup(s).