Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>,
	linux-sound@vger.kernel.org, linux-omap@vger.kernel.org
Cc: Peter Ujfalusi <peter.ujfalusi@gmail.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v2] ASoC: ti: omap3pandora: update board check to use DT compatible
Date: Sun, 10 May 2026 15:23:01 +0300	[thread overview]
Message-ID: <08f59a1e-76bd-4847-a0f8-c8690246e6f5@bitmer.com> (raw)
In-Reply-To: <CADkSEUi0U1oKsxZ9YmgG6wh8rc=RK37wUgq-bmA5XUn3aYSuAA@mail.gmail.com>

On 10/05/2026 8:47 am, Ethan Nelson-Moore wrote:
> On Sat, May 9, 2026 at 10:40 PM Ethan Nelson-Moore
> <enelsonmoore@gmail.com> wrote:
>> ---
>> Changes from v1: Fix mistake in commit message and remove Fixes tags -
>> machine ID checks still work with DT booting if the bootloader passes
>> the ID
>>
>> Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>
>> ---
> I forgot to move my changelog below the --- generated by git
> format-patch. Sorry. Could whoever merges this fix that, or should I
> resend this patch tomorrow?

You may add if plan to resend:

Acked-by: Jarkko Nikula <jarkko.nikula@bitmer.com>

      reply	other threads:[~2026-05-10 12:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260510053939.564314-1-enelsonmoore@gmail.com>
2026-05-10  5:39 ` [PATCH v2] mfd: twl4030-power: update checks for specific boards to use the DT Ethan Nelson-Moore
2026-05-10  5:47   ` Ethan Nelson-Moore
2026-05-10  5:39 ` [PATCH v2] ASoC: ti: omap3pandora: update board check to use DT compatible Ethan Nelson-Moore
2026-05-10  5:47   ` Ethan Nelson-Moore
2026-05-10 12:23     ` Jarkko Nikula [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=08f59a1e-76bd-4847-a0f8-c8690246e6f5@bitmer.com \
    --to=jarkko.nikula@bitmer.com \
    --cc=broonie@kernel.org \
    --cc=enelsonmoore@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@gmail.com \
    --cc=tiwai@suse.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