From: Mark Brown <broonie@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Iuliana Prodan <iuliana.prodan@nxp.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Laurentiu Mihalcea <laurentiumihalcea111@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH v3 0/7] Refactor imx drivers and introduce support for imx95
Date: Mon, 10 Feb 2025 16:30:09 +0000 [thread overview]
Message-ID: <173920500928.65690.14990676998915494188.b4-ty@kernel.org> (raw)
In-Reply-To: <20250207162246.3104-1-laurentiumihalcea111@gmail.com>
On Fri, 07 Feb 2025 11:22:39 -0500, Laurentiu Mihalcea wrote:
> A rather aggressive but arguably much needed refactorization of the SOF
> imx drivers. The refactorization is meant to address the code duplication
> in the imx drivers and decrease the coding effort required for introducing
> a new imx platform.
>
> After refactorization and imx95 introduction, only two drivers remain:
> imx8 (meant for the imx8 series: imx8 (imx8qm), imx8x (imx8qxp), imx8m,
> and imx8ulp) and imx9 (meant for the imx9 series: imx95 (for now)).
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: SOF: imx: introduce more common structures and functions
commit: 651e0ed391b148f83afba0bfbd8a56e38e58c34d
[2/7] ASoC: SOF: imx8: use common imx chip interface
commit: 645753d01356ff1a756812f1c69c53eb5c9081cd
[3/7] ASoC: SOF: imx8: use IMX_SOF_* macros
commit: 563e40153a56cbfae8721f9591022df5d930f939
[4/7] ASoC: SOF: imx8: drop unneeded/unused macros/header includes
commit: 45e02edd8422b6c4a511f38403dbd805cd139733
[5/7] ASoC: SOF: imx: merge imx8 and imx8m drivers
commit: 896530b7b0c08ee8b3296d5f012bfe1b0a979b86
[6/7] ASoC: SOF: imx: merge imx8 and imx8ulp drivers
commit: 07e3e514dd385300bd08da4a8df09240d272821e
[7/7] ASoC: SOF: imx: add driver for the imx95 chip
commit: 6cf5df1040ba0694aea6a5edc6f31811a442ea36
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:[~2025-02-10 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 16:22 [PATCH v3 0/7] Refactor imx drivers and introduce support for imx95 Laurentiu Mihalcea
2025-02-07 16:22 ` [PATCH v3 1/7] ASoC: SOF: imx: introduce more common structures and functions Laurentiu Mihalcea
2025-02-07 16:35 ` Markus Elfring
2025-02-07 16:22 ` [PATCH v3 2/7] ASoC: SOF: imx8: use common imx chip interface Laurentiu Mihalcea
2025-02-07 16:22 ` [PATCH v3 3/7] ASoC: SOF: imx8: use IMX_SOF_* macros Laurentiu Mihalcea
2025-02-07 16:22 ` [PATCH v3 4/7] ASoC: SOF: imx8: drop unneeded/unused macros/header includes Laurentiu Mihalcea
2025-02-07 16:22 ` [PATCH v3 5/7] ASoC: SOF: imx: merge imx8 and imx8m drivers Laurentiu Mihalcea
2025-02-07 16:22 ` [PATCH v3 6/7] ASoC: SOF: imx: merge imx8 and imx8ulp drivers Laurentiu Mihalcea
2025-02-07 16:22 ` [PATCH v3 7/7] ASoC: SOF: imx: add driver for the imx95 chip Laurentiu Mihalcea
2025-02-10 16:30 ` 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=173920500928.65690.14990676998915494188.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=imx@lists.linux.dev \
--cc=iuliana.prodan@nxp.com \
--cc=laurentiumihalcea111@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox