mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: jiaxin.yu@mediatek.com, angelogioacchino.delregno@collabora.com,
	robh+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	tzungbi@google.com, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org, julianbraha@gmail.com,
	trevor.wu@mediatek.com, linux-mediatek@lists.infradead.org,
	matthias.bgg@gmail.com, aaronyu@google.com,
	Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v10 0/8] ASoC: mediatek: Add support for MT8186 SoC
Date: Thu, 21 Jul 2022 00:12:17 +0100	[thread overview]
Message-ID: <165835873701.1007579.13802197177165168890.b4-ty@kernel.org> (raw)
In-Reply-To: <20220718162204.26238-1-jiaxin.yu@mediatek.com>

On Tue, 19 Jul 2022 00:21:56 +0800, Jiaxin Yu wrote:
> This series of patches adds support for Mediatek AFE of MT8186 Soc.
> Patches are based on broonie tree "for-next" branch.
> 
> Changes since v9:
>   - Drop the definitions that unused in mt8186-afe-common.h.
>   - Use device_get_match_data() instead of of_device_get_match_data().
> 
> [...]

Applied to

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

Thanks!

[1/8] dt-bindings: mediatek: mt6358: add new compatible for using mt6366
      commit: 8f57d8b149b1e46b4ffa707634fe76532ec89e83
[2/8] ASoC: mediatek: mt8186: add platform driver
      commit: 097e874ad3fc69601e2b142ff3b638893c355b41
[3/8] ASoC: mediatek: mt8186: add mt8186-mt6366 common driver
      commit: a809ded89d1d982ac05d8a3c6c943b49ff1b94fa
[4/8] dt-bindings: mediatek: mt8186: add audio afe document
      commit: 344afef6b980be569f4e9325778ca6869fed82cd
[5/8] ASoC: mediatek: mt8186: add machine driver with mt6366, da7219 and max98357
      commit: 3c6e24b65b53ce22c30492b9f239853b01d2d5b2
[6/8] dt-bindings: mediatek: mt8186: add mt8186-mt6366-da7219-max98357 document
      commit: 8a8da1e6af18f51b719a142fde92e5db56a129a0
[7/8] ASoC: mediatek: mt8186: add machine driver with mt6366, rt1019 and rt5682s
      commit: 0da16e370dd7a17b33b6fa2769ad9536389a0e12
[8/8] dt-bindings: mediatek: mt8186: add mt8186-mt6366-rt1019-rt5682s document
      commit: 1bcca73ee596e46e84782514621062c0ddf9d24f

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

      parent reply	other threads:[~2022-07-20 23:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 16:21 Jiaxin Yu
2022-07-18 16:21 ` [PATCH v10 1/8] dt-bindings: mediatek: mt6358: add new compatible for using mt6366 Jiaxin Yu
2022-07-18 16:21 ` [PATCH v10 2/8] ASoC: mediatek: mt8186: add platform driver Jiaxin Yu
2022-07-18 16:21 ` [PATCH v10 3/8] ASoC: mediatek: mt8186: add mt8186-mt6366 common driver Jiaxin Yu
2022-07-18 16:22 ` [PATCH v10 4/8] dt-bindings: mediatek: mt8186: add audio afe document Jiaxin Yu
2022-07-18 16:22 ` [PATCH v10 5/8] ASoC: mediatek: mt8186: add machine driver with mt6366, da7219 and max98357 Jiaxin Yu
2022-07-18 16:22 ` [PATCH v10 6/8] dt-bindings: mediatek: mt8186: add mt8186-mt6366-da7219-max98357 document Jiaxin Yu
2022-07-18 16:22 ` [PATCH v10 7/8] ASoC: mediatek: mt8186: add machine driver with mt6366, rt1019 and rt5682s Jiaxin Yu
2022-07-18 16:22 ` [PATCH v10 8/8] dt-bindings: mediatek: mt8186: add mt8186-mt6366-rt1019-rt5682s document Jiaxin Yu
2022-07-20 23:12 ` 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=165835873701.1007579.13802197177165168890.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=aaronyu@google.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jiaxin.yu@mediatek.com \
    --cc=julianbraha@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=trevor.wu@mediatek.com \
    --cc=tzungbi@google.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®