Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   Mark Brown <broonie@kernel.org>
To:     akihiko.odaki@gmail.com
Cc:     oder_chiou@realtek.com, perex@perex.cz,
        linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
        alsa-devel@alsa-project.org
In-Reply-To: <20220408041114.6024-1-akihiko.odaki@gmail.com>
References: <20220408041114.6024-1-akihiko.odaki@gmail.com>
Subject: Re: [PATCH] ASoC: soc-card: Create jack kcontrol without pins
Message-Id: <164995786974.2810970.8441162989456904692.b4-ty@kernel.org>
Date:   Thu, 14 Apr 2022 18:37:49 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 8 Apr 2022 13:11:14 +0900, Akihiko Odaki wrote:
> snd_soc_card_jack_new() allowed to create jack kcontrol without pins,
> but did not create kcontrols. The jack would not have kcontrols if pins
> were not going to be added.
> 
> This renames the old snd_soc_card_jack_new() to
> snd_soc_card_jack_new_pins() for use when pins are provided or will be
> added later. The new snd_soc_card_jack_new() appropriately creates a
> jack for use without pins and adds a kcontrol.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: soc-card: Create jack kcontrol without pins
      commit: 19aed2d6cdb72a7c92909832b9480d9cadebeef9

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