From: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@intel.com>,
sound-open-firmware@alsa-project.org
Subject: Re: [PATCH 0/2] ASoC: SOF: initialise work immediately
Date: Wed, 25 Mar 2020 12:10:12 +0100 [thread overview]
Message-ID: <20200325111012.GA7131@ubuntu> (raw)
In-Reply-To: <20200324133042.GB7039@sirena.org.uk>
Hi Mark,
On Tue, Mar 24, 2020 at 01:30:42PM +0000, Mark Brown wrote:
> On Tue, Mar 24, 2020 at 01:29:19PM +0100, Guennadi Liakhovetski wrote:
> > Fix uninitialised work errors by moving initialisation to directly
> > after allocation.
> >
> > Guennadi Liakhovetski (2):
> > ASoC: SOF: (cosmetic) use for_each_pcm_streams() in sof_dai_load()
> > ASoC: SOF: fix uninitialised "work" with VirtIO
>
> As documented in submitting-patches.rst please send patches to the
> maintainers for the code you would like to change. The normal kernel
> workflow is that people apply patches from their inboxes, if they aren't
> copied they are likely to not see the patch at all and it is much more
> difficult to apply patches.
An update: these patches got merged into the SOF tree, so, no need to
merge them to ASoC directly.
Thanks
Guennadi
next prev parent reply other threads:[~2020-03-25 11:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 12:29 [PATCH 0/2] ASoC: SOF: initialise work immediately Guennadi Liakhovetski
2020-03-24 12:29 ` [PATCH 1/2] ASoC: SOF: (cosmetic) use for_each_pcm_streams() in sof_dai_load() Guennadi Liakhovetski
2020-03-24 13:29 ` Pierre-Louis Bossart
2020-03-24 14:06 ` Guennadi Liakhovetski
2020-03-24 12:29 ` [PATCH 2/2] ASoC: SOF: fix uninitialised "work" with VirtIO Guennadi Liakhovetski
2020-03-24 13:30 ` [PATCH 0/2] ASoC: SOF: initialise work immediately Mark Brown
2020-03-24 13:58 ` Guennadi Liakhovetski
2020-03-24 14:48 ` Mark Brown
2020-03-25 11:10 ` Guennadi Liakhovetski
2020-03-25 11:10 ` Guennadi Liakhovetski [this message]
2020-03-25 11:20 ` 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=20200325111012.GA7131@ubuntu \
--to=guennadi.liakhovetski@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.de \
/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