From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
Chintan Patel <chintan.m.patel@intel.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [GIT PULL] ASoC fixes for v4.14
Date: Tue, 31 Oct 2017 13:34:47 +0530 [thread overview]
Message-ID: <20171031080447.GL3187@localhost> (raw)
In-Reply-To: <20171027063916.xkhmpk673eqh7424@sirena.org.uk>
On Fri, Oct 27, 2017 at 08:39:16AM +0200, Mark Brown wrote:
> On Thu, Oct 26, 2017 at 09:39:39PM +0200, Takashi Iwai wrote:
>
> > IMO, my PCM unbind workaround can be postponed to 4.15, as the unbind
> > is still broken even with this. It can be combined with other unbind
> > fixes.
>
> > Also, topology fixes are only potential issues, and no urgent fixes
> > for the bugs we're hitting now. So they can be postponed, too.
>
> For me I'd prioritize getting things into the core over other things
> (and both fixes are small) but these are the ones you want to drop. I'd
> say the topology bugs are just straight up bugs, someone with the
> ability to replace the topology file can readily trigger them (as could
> disk corruption) and the null pointer dereference is definitely severe
> enough that we should just fix it.
>
> I guess we could try to drop all the resource leak fixes but several of
> them are in with other patches in branches.
>
> > One Skylake jack name fix is actually wrong.
> > It sets "HDMI/DP, pcm=%d Jack", but the right name is without space,
> > i.e. "HDMI/DP,pcm=%d Jack".
>
> So how did they test that fix then... bah.
Oops, this came from Chrome, so I guess CRAS is happy with space.
I will send fix and yes they can goto next merge window.
Sorry for the miss
--
~Vinod
prev parent reply other threads:[~2017-10-31 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 14:13 [GIT PULL] ASoC fixes for v4.14 Mark Brown
2017-10-26 19:39 ` Takashi Iwai
2017-10-27 6:39 ` Mark Brown
2017-10-31 8:04 ` Vinod Koul [this message]
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=20171031080447.GL3187@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=chintan.m.patel@intel.com \
--cc=lgirdwood@gmail.com \
--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