From: Mark Brown <broonie@kernel.org>
To: codrin.ciubotariu@microchip.com, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org
Cc: tiwai@suse.com, sha@pengutronix.de, perex@perex.cz,
alexandre.belloni@bootlin.com
Subject: Re: [PATCH 1/2] Revert "ASoC: dmaengine: do not use a NULL prepare_slave_config() callback"
Date: Mon, 25 Apr 2022 17:00:18 +0100 [thread overview]
Message-ID: <165090241813.345430.3503254961552314811.b4-ty@kernel.org> (raw)
In-Reply-To: <20220421125403.2180824-1-codrin.ciubotariu@microchip.com>
On Thu, 21 Apr 2022 15:54:02 +0300, Codrin Ciubotariu wrote:
> This reverts commit 9a1e13440a4f2e7566fd4c5eae6a53e6400e08a4.
>
> As pointed out by Sascha Hauer, this patch changes:
> if (pmc->config && !pcm->config->prepare_slave_config)
> <do nothing>
> to:
> if (pmc->config && !pcm->config->prepare_slave_config)
> snd_dmaengine_pcm_prepare_slave_config()
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] Revert "ASoC: dmaengine: do not use a NULL prepare_slave_config() callback"
commit: 660564fc9a92a893a14f255be434f7ea0b967901
[2/2] ASoC: atmel: mchp-pdmc: set prepare_slave_config
commit: 2bde1985e39173d8cb64005dad6f34e9bee4c750
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
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: codrin.ciubotariu@microchip.com, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org
Cc: alexandre.belloni@bootlin.com, tiwai@suse.com, sha@pengutronix.de
Subject: Re: [PATCH 1/2] Revert "ASoC: dmaengine: do not use a NULL prepare_slave_config() callback"
Date: Mon, 25 Apr 2022 17:00:18 +0100 [thread overview]
Message-ID: <165090241813.345430.3503254961552314811.b4-ty@kernel.org> (raw)
In-Reply-To: <20220421125403.2180824-1-codrin.ciubotariu@microchip.com>
On Thu, 21 Apr 2022 15:54:02 +0300, Codrin Ciubotariu wrote:
> This reverts commit 9a1e13440a4f2e7566fd4c5eae6a53e6400e08a4.
>
> As pointed out by Sascha Hauer, this patch changes:
> if (pmc->config && !pcm->config->prepare_slave_config)
> <do nothing>
> to:
> if (pmc->config && !pcm->config->prepare_slave_config)
> snd_dmaengine_pcm_prepare_slave_config()
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] Revert "ASoC: dmaengine: do not use a NULL prepare_slave_config() callback"
commit: 660564fc9a92a893a14f255be434f7ea0b967901
[2/2] ASoC: atmel: mchp-pdmc: set prepare_slave_config
commit: 2bde1985e39173d8cb64005dad6f34e9bee4c750
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
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: codrin.ciubotariu@microchip.com, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org
Cc: tiwai@suse.com, sha@pengutronix.de, perex@perex.cz,
alexandre.belloni@bootlin.com
Subject: Re: [PATCH 1/2] Revert "ASoC: dmaengine: do not use a NULL prepare_slave_config() callback"
Date: Mon, 25 Apr 2022 17:00:18 +0100 [thread overview]
Message-ID: <165090241813.345430.3503254961552314811.b4-ty@kernel.org> (raw)
In-Reply-To: <20220421125403.2180824-1-codrin.ciubotariu@microchip.com>
On Thu, 21 Apr 2022 15:54:02 +0300, Codrin Ciubotariu wrote:
> This reverts commit 9a1e13440a4f2e7566fd4c5eae6a53e6400e08a4.
>
> As pointed out by Sascha Hauer, this patch changes:
> if (pmc->config && !pcm->config->prepare_slave_config)
> <do nothing>
> to:
> if (pmc->config && !pcm->config->prepare_slave_config)
> snd_dmaengine_pcm_prepare_slave_config()
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] Revert "ASoC: dmaengine: do not use a NULL prepare_slave_config() callback"
commit: 660564fc9a92a893a14f255be434f7ea0b967901
[2/2] ASoC: atmel: mchp-pdmc: set prepare_slave_config
commit: 2bde1985e39173d8cb64005dad6f34e9bee4c750
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-25 16:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 12:54 [PATCH 1/2] Revert "ASoC: dmaengine: do not use a NULL prepare_slave_config() callback" Codrin Ciubotariu
2022-04-21 12:54 ` Codrin Ciubotariu
2022-04-21 12:54 ` Codrin Ciubotariu
2022-04-21 12:54 ` [PATCH 2/2] ASoC: atmel: mchp-pdmc: set prepare_slave_config Codrin Ciubotariu
2022-04-21 12:54 ` Codrin Ciubotariu
2022-04-21 12:54 ` Codrin Ciubotariu
2022-04-25 16:00 ` Mark Brown [this message]
2022-04-25 16:00 ` [PATCH 1/2] Revert "ASoC: dmaengine: do not use a NULL prepare_slave_config() callback" Mark Brown
2022-04-25 16:00 ` Mark Brown
2022-04-25 16:00 ` Mark Brown
2022-04-25 16:00 ` Mark Brown
2022-04-25 16:00 ` Mark Brown
2022-04-26 7:42 ` Codrin.Ciubotariu
2022-04-26 7:42 ` Codrin.Ciubotariu
2022-04-26 7:42 ` Codrin.Ciubotariu
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=165090241813.345430.3503254961552314811.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=codrin.ciubotariu@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sha@pengutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.