mbox series

[0/2] ASoC: Intel: soc-acpi-intel-tgl/mtl-match: declare adr as ull

Message ID 20250204033134.92332-1-yung-chuan.liao@linux.intel.com (mailing list archive)
Headers show
Series ASoC: Intel: soc-acpi-intel-tgl/mtl-match: declare adr as ull | expand

Message

Bard Liao Feb. 4, 2025, 3:31 a.m. UTC
The adr is u64.

Bard Liao (2):
  ASoC: Intel: soc-acpi-intel-tgl-match: declare adr as ull
  ASoC: Intel: soc-acpi-intel-mtl-match: declare adr as ull

 .../soc/intel/common/soc-acpi-intel-mtl-match.c  |  2 +-
 .../soc/intel/common/soc-acpi-intel-tgl-match.c  | 16 ++++++++--------
 2 files changed, 9 insertions(+), 9 deletions(-)

Comments

Mark Brown Feb. 5, 2025, 12:44 p.m. UTC | #1
On Tue, 04 Feb 2025 11:31:32 +0800, Bard Liao wrote:
> The adr is u64.
> 
> Bard Liao (2):
>   ASoC: Intel: soc-acpi-intel-tgl-match: declare adr as ull
>   ASoC: Intel: soc-acpi-intel-mtl-match: declare adr as ull
> 
> .../soc/intel/common/soc-acpi-intel-mtl-match.c  |  2 +-
>  .../soc/intel/common/soc-acpi-intel-tgl-match.c  | 16 ++++++++--------
>  2 files changed, 9 insertions(+), 9 deletions(-)
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: Intel: soc-acpi-intel-tgl-match: declare adr as ull
      commit: 3588b76db7ba798f54dee39a55708b16e1c61de4
[2/2] ASoC: Intel: soc-acpi-intel-mtl-match: declare adr as ull
      commit: 20efccc53abf99fa52ea30a43dec758f6b6b9940

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