linux-kernel - Re: [PATCH 1/2] ASoC: SOF: amd: move iram-dram fence register programming sequence

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: <f76c7f8e-f4e7-4ac6-87e1-1ba9b2b19a82@web.de>
Date: Tue, 13 Aug 2024 10:15:27 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>, linux-sound@...r.kernel.org,
 alsa-devel@...a-project.org, sound-open-firmware@...a-project.org,
 Mark Brown <broonie@...nel.org>,
 Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
 Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
 Ajit Kumar Pandey <AjitKumar.Pandey@....com>,
 Bard Liao <yung-chuan.liao@...ux.intel.com>,
 Basavaraj Hiregoudar <Basavaraj.Hiregoudar@....com>,
 Cristian Ciocaltea <cristian.ciocaltea@...labora.com>,
 Daniel Baluta <daniel.baluta@....com>, Jaroslav Kysela <perex@...ex.cz>,
 Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
 Sunil-kumar Dommati <Sunil-kumar.Dommati@....com>,
 Liam Girdwood <lgirdwood@...il.com>,
 Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
 Takashi Iwai <tiwai@...e.com>,
 Venkata Prasad Potturu <venkataprasad.potturu@....com>
Subject: Re: [PATCH 1/2] ASoC: SOF: amd: move iram-dram fence register
 programming sequence

…
> before triggering SHA dma. This ensures that IRAM size will programmed
> correctly before initiaing SHA dma.

Please improve such a change description with an imperative wording.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.11-rc2#n94

Please avoid typos accordingly.

Regards,
Markus