linux-kernel - Re: [PATCH 11/11] ASoC: SOF: topology: Add new DAI type entry for SOF_DAI_AMD

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: <9fc36923-8387-4c86-bb04-8c71a826adb1@sirena.org.uk>
Date: Fri, 15 Dec 2023 12:53:39 +0000
From: Mark Brown <broonie@...nel.org>
To: Cristian Ciocaltea <cristian.ciocaltea@...labora.com>
Cc: Venkata Prasad Potturu <venkataprasad.potturu@....com>,
	Liam Girdwood <lgirdwood@...il.com>,
	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.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>,
	Alper Nebi Yasak <alpernebiyasak@...il.com>,
	Syed Saba Kareem <Syed.SabaKareem@....com>,
	Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
	Marian Postevca <posteuca@...ex.one>,
	Vijendar Mukunda <Vijendar.Mukunda@....com>,
	V sujith kumar Reddy <Vsujithkumar.Reddy@....com>,
	Mastan Katragadda <Mastan.Katragadda@....com>,
	Ajit Kumar Pandey <AjitKumar.Pandey@....com>,
	linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
	sound-open-firmware@...a-project.org, kernel@...labora.com
Subject: Re: [PATCH 11/11] ASoC: SOF: topology: Add new DAI type entry for
 SOF_DAI_AMD_BT

On Fri, Dec 15, 2023 at 12:57:34PM +0200, Cristian Ciocaltea wrote:

> If the SOF workflow is unable to integrate fixes submitted upstream, I
> would perceive that as a significant drawback of adhering to that
> process.  It is hard to believe, though, that this is really the case.

As far as I'm aware they can cope fine with that, though it does help if
people try to avoid needless collisions.  It *does* cause trouble to use
both github and upstream flows simultaneously and there's a preference
for pushing anything substantial through github but picking one or the
other works as far as I know.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)