Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-stable <stable@vger.kernel.org>,
	Sasha Levin <sashal@kernel.org>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	Mark Brown <broonie@kernel.org>
Subject: Re: Please apply to v6.14.x commit 6eab70345799 ("ASoC: soc-core: Stop using of_property_read_bool() for non-boolean properties")
Date: Mon, 5 May 2025 15:27:18 +0200	[thread overview]
Message-ID: <8e6c91c0-6780-414e-9cf6-1cc2a058be0b@csgroup.eu> (raw)
In-Reply-To: <2025050556-blurred-graves-b443@gregkh>



Le 05/05/2025 à 15:10, Greg Kroah-Hartman a écrit :
> On Mon, May 05, 2025 at 11:48:45AM +0000, LEROY Christophe wrote:
>> Hi,
>>
>> Could you please apply commit 6eab70345799 ("ASoC: soc-core: Stop using
>> of_property_read_bool() for non-boolean properties") to v6.14.x in order
>> to silence warnings introduced in v6.14 by commit c141ecc3cecd ("of:
>> Warn when of_property_read_bool() is used on non-boolean properties")
> 
> What about 6.12.y and 6.6.y as well?  It's in the following released
> kernels:
> 	6.6.84 6.12.20 6.13.8 6.14
> 

Ah ! it has been applied to stable versions allthough it doesn't carry a 
Fixes: tag.

So yes the 'fix' to ASoC should then be applied as well to stable 
versions to avoid the warning.

Note that it doesn't cherry-pick cleanly to 6.6.84, you'll first need 
commit 69dd15a8ef0a ("ASoC: Use of_property_read_bool()")

Christophe

  parent reply	other threads:[~2025-05-05 13:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 11:48 Please apply to v6.14.x commit 6eab70345799 ("ASoC: soc-core: Stop using of_property_read_bool() for non-boolean properties") LEROY Christophe
2025-05-05 13:10 ` Greg Kroah-Hartman
2025-05-05 13:26   ` LEROY Christophe
2025-05-05 13:27   ` Christophe Leroy [this message]
2025-05-05 14:23     ` Greg Kroah-Hartman

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=8e6c91c0-6780-414e-9cf6-1cc2a058be0b@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.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