LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
	Aakash Hemadri <aakashhemadri123@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>,
	linux-tegra@vger.kernel.org, Bjorn Helgaas <bjorn@helgaas.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Jawoslav Kysela <perex@perex.cz>,
	Thierry Reding <thierry.reding@gmail.com>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ASoC: tegra: Use of_device_get_match_data
Date: Mon, 16 Aug 2021 18:04:40 +0100	[thread overview]
Message-ID: <162913223312.13582.10888100799475599538.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1628971397.git.aakashhemadri123@gmail.com>

On Sun, 15 Aug 2021 01:42:17 +0530, Aakash Hemadri wrote:
> 	Prefer `of_device_get_match_data` over `of_match_device`. This patch
> replaces of_match_device with of_device_get_match_data.
> 
> This patch series will apply cleanly on for-next
> 
> Aakash Hemadri (2):
>   ASoC: tegra30: ahub: Use of_device_get_match_data
>   ASoC: tegra30: i2s: Use of_device_get_match_data
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: tegra30: ahub: Use of_device_get_match_data
      commit: 80165bb8043391f4ef4916bde947a4d805a54aa6
[2/2] ASoC: tegra30: i2s: Use of_device_get_match_data
      commit: 356b94a32a75203616e5a7c3cd2b19101bc87086

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:[~2021-08-16 17:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-14 20:12 Aakash Hemadri
2021-08-14 20:12 ` [PATCH 1/2] ASoC: tegra30: ahub: " Aakash Hemadri
2021-08-16  9:54   ` Thierry Reding
2021-08-16 18:02   ` Bjorn Helgaas
2021-08-16 18:39   ` Mark Brown
2021-08-16 19:46     ` Aakash Hemadri
2021-08-16 19:49       ` Mark Brown
2021-08-16 19:58         ` Aakash Hemadri
2021-08-17 13:52     ` Thierry Reding
2021-08-14 20:12 ` [PATCH 2/2] ASoC: tegra30: i2s: " Aakash Hemadri
2021-08-16  9:54   ` Thierry Reding
2021-08-16 17:04 ` 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=162913223312.13582.10888100799475599538.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=aakashhemadri123@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bjorn@helgaas.com \
    --cc=jonathanh@nvidia.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=perex@perex.cz \
    --cc=skhan@linuxfoundation.org \
    --cc=thierry.reding@gmail.com \
    --cc=tiwai@suse.com \
    --subject='Re: [PATCH 0/2] ASoC: tegra: Use of_device_get_match_data' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).