mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
Cc: Mastan Katragadda <Mastan.Katragadda@amd.com>,
	alsa-devel@alsa-project.org, Basavaraj.Hiregoudar@amd.com,
	Sunil-kumar.Dommati@amd.com, Arungopal.kondaveeti@amd.com,
	vsujithkumar.reddy@amd.com, venkataprasad.potturu@amd.com,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Ajit Kumar Pandey <AjitKumar.Pandey@amd.com>,
	Ajye Huang <ajye_huang@compal.corp-partner.google.com>,
	"moderated list:SOUND - SOUND OPEN FIRMWARE (SOF) DRIVERS" 
	<sound-open-firmware@alsa-project.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: (subset) [PATCH 1/2] ASoC: SOF: amd: add revision check for sending sha dma completion command
Date: Mon, 3 Jul 2023 17:10:50 +0100	[thread overview]
Message-ID: <2adeaea7-e3ef-4a58-bdd2-18d3ca3e2519@sirena.org.uk> (raw)
In-Reply-To: <cafff012-54ac-2d15-1e76-c5313c01f834@amd.com>

[-- Attachment #1: Type: text/plain, Size: 496 bytes --]

On Mon, Jul 03, 2023 at 08:58:17PM +0530, Mukunda,Vijendar wrote:
> On 30/06/23 22:37, Mark Brown wrote:

> > Thanks!
> >
> > [1/2] ASoC: SOF: amd: add revision check for sending sha dma completion command
> >       commit: b1db244c716fe300e36428aeb0874913d2e0a91d

> It looks like second patch didn't get merged in this series.
> Do we need to resend the second patch?

I don't know off hand what that second patch was.  If it wasn't a bug
fix it'll just be waiting till after the merge window.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-07-03 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  7:05 Mastan Katragadda
2023-06-30  7:05 ` [PATCH 2/2] ASoC: SOF: amd: refactor PSP smn_read Mastan Katragadda
2023-07-12 11:08   ` Mastan Katragadda
2023-07-12 11:40     ` Mark Brown
2023-06-30 17:07 ` (subset) [PATCH 1/2] ASoC: SOF: amd: add revision check for sending sha dma completion command Mark Brown
2023-07-03 15:28   ` Mukunda,Vijendar
2023-07-03 16:10     ` Mark Brown [this message]
2023-07-12  3:33       ` Mastan Katragadda
2023-07-12 11:04         ` Mark Brown
2023-07-12 11:47 ` 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=2adeaea7-e3ef-4a58-bdd2-18d3ca3e2519@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=AjitKumar.Pandey@amd.com \
    --cc=Arungopal.kondaveeti@amd.com \
    --cc=Basavaraj.Hiregoudar@amd.com \
    --cc=Mastan.Katragadda@amd.com \
    --cc=Sunil-kumar.Dommati@amd.com \
    --cc=ajye_huang@compal.corp-partner.google.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=daniel.baluta@nxp.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=sound-open-firmware@alsa-project.org \
    --cc=tiwai@suse.com \
    --cc=venkataprasad.potturu@amd.com \
    --cc=vijendar.mukunda@amd.com \
    --cc=vsujithkumar.reddy@amd.com \
    --cc=yung-chuan.liao@linux.intel.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®