All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>,
	alsa-devel@alsa-project.org
Cc: Jaroslav Kysela <perex@perex.cz>,
	Liam Girdwood <lgirdwood@gmail.com>,
	open list <linux-kernel@vger.kernel.org>,
	Basavaraj.Hiregoudar@amd.com, Takashi Iwai <tiwai@suse.com>,
	Alexander.Deucher@amd.com, Sunil-kumar.Dommati@amd.com,
	V sujith kumar Reddy <vsujithkumar.reddy@amd.com>,
	Vijendar.Mukunda@amd.com
Subject: Re: [PATCH] ASoC: amd: acp: acp-mach: Change default RT1019 amp dev id
Date: Thu, 06 Jan 2022 20:28:17 +0000	[thread overview]
Message-ID: <164150089750.2243486.8547152917333843393.b4-ty@kernel.org> (raw)
In-Reply-To: <20220106150525.396170-1-AjitKumar.Pandey@amd.com>

On Thu, 6 Jan 2022 20:35:21 +0530, Ajit Kumar Pandey wrote:
> RT1019 components was initially registered with i2c1 and i2c2 but
> now changed to i2c0 and i2c1 in most of our AMD platforms. Change
> default rt1019 components to 10EC1019:00 and 10EC1019:01 which is
> aligned with most of AMD machines.
> 
> Any exception to rt1019 device ids in near future board design can
> be handled using dmi based quirk for that machine.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: amd: acp: acp-mach: Change default RT1019 amp dev id
      commit: 7112550890d7e415188a3351ec0a140be60f6deb

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: Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>,
	alsa-devel@alsa-project.org
Cc: Sunil-kumar.Dommati@amd.com, Liam Girdwood <lgirdwood@gmail.com>,
	Basavaraj.Hiregoudar@amd.com,
	open list <linux-kernel@vger.kernel.org>,
	Takashi Iwai <tiwai@suse.com>,
	V sujith kumar Reddy <vsujithkumar.reddy@amd.com>,
	Vijendar.Mukunda@amd.com, Alexander.Deucher@amd.com
Subject: Re: [PATCH] ASoC: amd: acp: acp-mach: Change default RT1019 amp dev id
Date: Thu, 06 Jan 2022 20:28:17 +0000	[thread overview]
Message-ID: <164150089750.2243486.8547152917333843393.b4-ty@kernel.org> (raw)
In-Reply-To: <20220106150525.396170-1-AjitKumar.Pandey@amd.com>

On Thu, 6 Jan 2022 20:35:21 +0530, Ajit Kumar Pandey wrote:
> RT1019 components was initially registered with i2c1 and i2c2 but
> now changed to i2c0 and i2c1 in most of our AMD platforms. Change
> default rt1019 components to 10EC1019:00 and 10EC1019:01 which is
> aligned with most of AMD machines.
> 
> Any exception to rt1019 device ids in near future board design can
> be handled using dmi based quirk for that machine.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: amd: acp: acp-mach: Change default RT1019 amp dev id
      commit: 7112550890d7e415188a3351ec0a140be60f6deb

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

  reply	other threads:[~2022-01-06 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 15:05 [PATCH] ASoC: amd: acp: acp-mach: Change default RT1019 amp dev id Ajit Kumar Pandey
2022-01-06 15:05 ` Ajit Kumar Pandey
2022-01-06 20:28 ` Mark Brown [this message]
2022-01-06 20:28   ` Mark Brown

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=164150089750.2243486.8547152917333843393.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=AjitKumar.Pandey@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Basavaraj.Hiregoudar@amd.com \
    --cc=Sunil-kumar.Dommati@amd.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=vsujithkumar.reddy@amd.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.