From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, pierre-louis.bossart@linux.intel.com,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
daniel.baluta@nxp.com, ranjani.sridharan@linux.intel.com,
kai.vehmanen@linux.intel.com
Subject: Re: [PATCH] ASoC: SOF: Rename sof_arch_ops to dsp_arch_ops
Date: Fri, 17 Sep 2021 15:03:43 +0100 [thread overview]
Message-ID: <163188719814.50326.7112332224591931711.b4-ty@kernel.org> (raw)
In-Reply-To: <20210916130308.7969-1-peter.ujfalusi@linux.intel.com>
On Thu, 16 Sep 2021 16:03:08 +0300, Peter Ujfalusi wrote:
> From the name sof_arch_ops one can not decipher that these ops are DSP
> architecture ops.
> Rename it to dsp_arch_ops and change also the macro to retrieve the DSP
> architecture specific ops as well.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: SOF: Rename sof_arch_ops to dsp_arch_ops
commit: 0ed66cb7b6d38f0bab061466c1aa0e9f3db45e93
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:[~2021-09-17 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 13:03 [PATCH] ASoC: SOF: Rename sof_arch_ops to dsp_arch_ops Peter Ujfalusi
2021-09-17 14:03 ` 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=163188719814.50326.7112332224591931711.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.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.