lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ab3c2e81-b7f5-9527-7e32-d332259cdc87@amd.com>
Date:   Wed, 12 Jul 2023 09:03:30 +0530
From:   Mastan Katragadda <mastan.katragadda@....com>
To:     Mark Brown <broonie@...nel.org>,
        "Mukunda,Vijendar" <vijendar.mukunda@....com>
Cc:     alsa-devel@...a-project.org, Basavaraj.Hiregoudar@....com,
        Sunil-kumar.Dommati@....com, Arungopal.kondaveeti@....com,
        vsujithkumar.reddy@....com, venkataprasad.potturu@....com,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
        Bard Liao <yung-chuan.liao@...ux.intel.com>,
        Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
        Daniel Baluta <daniel.baluta@....com>,
        Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Ajit Kumar Pandey <AjitKumar.Pandey@....com>,
        Ajye Huang <ajye_huang@...pal.corp-partner.google.com>,
        "moderated list:SOUND - SOUND OPEN FIRMWARE (SOF) DRIVERS" 
        <sound-open-firmware@...a-project.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: (subset) [PATCH 1/2] ASoC: SOF: amd: add revision check for
 sending sha dma completion command


On 03/07/23 21:40, Mark Brown wrote:
> 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.
  Do I need to resend the second patch?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ