Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Emil Renner Berthing <emil.renner.berthing@canonical.com>
Cc: linux-riscv@lists.infradead.org, spersvold@gmail.com,
	paul.walmsley@sifive.com, linux-kernel@vger.kernel.org,
	jeremy.linton@arm.com, conor.dooley@microchip.com,
	palmer@dabbelt.com, cuiyunhui@bytedance.com,
	sudeep.holla@arm.com, mikisabate@gmail.com
Subject: Re: [PATCH v1] riscv: Use of_property_present() to test for non-boolean properties
Date: Thu, 13 Feb 2025 14:20:34 +0000	[thread overview]
Message-ID: <173945643426.1243861.13922610517205148727.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250205143903.413959-1-emil.renner.berthing@canonical.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed,  5 Feb 2025 15:39:01 +0100 you wrote:
> The use of of_property_read_bool() for non-boolean properties is
> deprecated and since
> 
> commit c141ecc3cecd ("of: Warn when of_property_read_bool() is used on non-boolean properties")
> 
> a warning is displayed when used incorrectly. Fix it by switching to
> of_property_present() as recommended in the same commit.
> 
> [...]

Here is the summary with links:
  - [v1] riscv: Use of_property_present() to test for non-boolean properties
    https://git.kernel.org/riscv/c/b9524a73725d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

      parent reply	other threads:[~2025-02-13 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 14:39 [PATCH v1] riscv: Use of_property_present() to test for non-boolean properties Emil Renner Berthing
2025-02-05 19:47 ` Ron Economos
2025-02-05 23:23 ` Jeremy Linton
2025-02-11  7:55 ` Alexandre Ghiti
2025-02-11  9:20   ` Emil Renner Berthing
2025-02-13 14:20 ` patchwork-bot+linux-riscv [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=173945643426.1243861.13922610517205148727.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=cuiyunhui@bytedance.com \
    --cc=emil.renner.berthing@canonical.com \
    --cc=jeremy.linton@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mikisabate@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=spersvold@gmail.com \
    --cc=sudeep.holla@arm.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