From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org,
Alexander Sverdlin <alexander.sverdlin@gmail.com>
Cc: Nikita Shubin <nikita.shubin@maquefel.me>,
David Rhodes <david.rhodes@cirrus.com>,
James Schulman <james.schulman@cirrus.com>,
Jaroslav Kysela <perex@perex.cz>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
Lucas Tanure <tanureal@opensource.cirrus.com>,
patches@opensource.cirrus.com,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH 0/3] ASoC: ep93xx: Prepare for DT transition
Date: Tue, 11 Apr 2023 15:19:04 +0100 [thread overview]
Message-ID: <168122274438.54453.12909974766938645863.b4-ty@kernel.org> (raw)
In-Reply-To: <20230410223902.2321834-1-alexander.sverdlin@gmail.com>
On Tue, 11 Apr 2023 00:38:59 +0200, Alexander Sverdlin wrote:
> This is a preparatory series for EP93xx transition to DT. This patchset is
> a pre-requisite and has been tested with the full DT patchset [1].
>
> [1]. git://git.maquefel.me/linux.git branch ep93xx/6.2-rc4-v0
>
> Alexander Sverdlin (3):
> ASoC: ep93xx: i2s: move enable call to startup callback
> ASoC: cs4271: flat regcache, trivial simplifications
> ASoC: ep93xx: i2s: Make it individually selectable
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: ep93xx: i2s: move enable call to startup callback
commit: 80f47122538d40b1a6a2c1a3c2d37b6e51b74224
[2/3] ASoC: cs4271: flat regcache, trivial simplifications
commit: 2e9688c81cfc48b210af6f313cb04589b7943e86
[3/3] ASoC: ep93xx: i2s: Make it individually selectable
commit: 24f934becf60598fdec9c9f2e06437c831ffa374
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
prev parent reply other threads:[~2023-04-11 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 22:38 Alexander Sverdlin
2023-04-10 22:39 ` [PATCH 1/3] ASoC: ep93xx: i2s: move enable call to startup callback Alexander Sverdlin
2023-04-11 11:39 ` Mark Brown
2023-04-10 22:39 ` [PATCH 2/3] ASoC: cs4271: flat regcache, trivial simplifications Alexander Sverdlin
2023-04-12 9:09 ` Charles Keepax
2023-04-10 22:39 ` [PATCH 3/3] ASoC: ep93xx: i2s: Make it individually selectable Alexander Sverdlin
2023-04-11 14:19 ` Mark Brown [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=168122274438.54453.12909974766938645863.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alexander.sverdlin@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.rhodes@cirrus.com \
--cc=james.schulman@cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita.shubin@maquefel.me \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=rf@opensource.cirrus.com \
--cc=tanureal@opensource.cirrus.com \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®