Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Mark Brown <broonie@kernel.org>
To:     krzk@kernel.org, rikard.falkeborn@gmail.com,
        Liam Girdwood <lgirdwood@gmail.com>, s.nawrocki@samsung.com
Cc:     Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
        Takashi Iwai <tiwai@suse.com>,
        Jaroslav Kysela <perex@perex.cz>, linux-kernel@vger.kernel.org,
        linux-actions@lists.infradead.org, afaerber@suse.de,
        linux-arm-kernel@lists.infradead.org, alsa-devel@alsa-project.org,
        mani@kernel.org
In-Reply-To: <20220330204227.25081-1-rikard.falkeborn@gmail.com>
References: <20220330204227.25081-1-rikard.falkeborn@gmail.com>
Subject: Re: [PATCH] ASoC: samsung: Constify snd_soc_dapm_{route,widget} structs
Message-Id: <164915109148.276574.7227991139286446163.b4-ty@kernel.org>
Date:   Tue, 05 Apr 2022 10:31:31 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 30 Mar 2022 22:42:27 +0200, Rikard Falkeborn wrote:
> These structs only have their address assigned to the
> dapm_{routes,widget} fields in the snd_soc_card struct,
> both which are pointers to const data. Make them const to
> allow the compiler to put them in read-only memory.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: samsung: Constify snd_soc_dapm_{route,widget} structs
      commit: 5449fd7bd01fc13266979a6ab48493d4d2e43725

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