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] [day] [month] [year] [list]
Message-ID: <dc173079-78b5-81e9-42ec-439954c00efb@microchip.com>
Date:   Tue, 26 Apr 2022 07:42:04 +0000
From:   <Codrin.Ciubotariu@...rochip.com>
To:     <broonie@...nel.org>
CC:     <alsa-devel@...a-project.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <perex@...ex.cz>, <tiwai@...e.com>,
        <alexandre.belloni@...tlin.com>, <sha@...gutronix.de>
Subject: Re: [PATCH 1/2] Revert "ASoC: dmaengine: do not use a NULL
 prepare_slave_config() callback"

On 25.04.2022 19:00, Mark Brown wrote:
> On Thu, Apr 21, 2022 at 03:54:02PM +0300, Codrin Ciubotariu wrote:
>> This reverts commit 9a1e13440a4f2e7566fd4c5eae6a53e6400e08a4.
>>
>> As pointed out by Sascha Hauer, this patch changes:
>> if (pmc->config && !pcm->config->prepare_slave_config)
> Please submit patches using subject lines reflecting the style for the
> subsystem, this makes it easier for people to identify relevant patches.
> Look at what existing commits in the area you're changing are doing and
> make sure your subject lines visually resemble what they're doing.
> There's no need to resubmit to fix this alone.

I did not know how to do properly do a revert. I saw some patches of 
Greg that were made with 'git revert'. I will remember for next time. 
Thanks for taking my patch anyway!

Best regards,
Codrin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ