Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [GIT PULL] ASoC fixes for v5.0
Date: Fri, 18 Jan 2019 16:09:18 +0100	[thread overview]
Message-ID: <s5hfttq0zq9.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190118125453.GB6260@sirena.org.uk>

On Fri, 18 Jan 2019 13:54:53 +0100,
Mark Brown wrote:
> 
> The following changes since commit a7a850dba82498a1e050d8d153cae67ce0edb3b2:
> 
>   Merge branch 'asoc-4.21' into asoc-next (2018-12-18 12:23:59 +0000)
> 
> are available in the Git repository at:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git tags/asoc-fix-v5.0-rc2
> 
> for you to fetch changes up to 4cb79ef9c6c4413427cd70afbb1f3bc01e9b7abf:
> 
>   ASoC: amd: Fix potential NULL pointer dereference (2019-01-15 19:06:23 +0000)
> 
> ----------------------------------------------------------------
> ASoC: Fixes for v5.0
> 
> Quite a big batch of fixes here.  There's a couple of things going on,
> the main one is that we found some issues with not deferring probe when
> we should, causing us to skip some driver initialization.  The fixes for
> this then in turn exposed some issues with how we were searching for
> components which had previously gone unnoticed due to the original
> issue.
> 
> There's also been the normal driver specific stuff and there's been what
> looks like several batches of automated scanning for issues which have
> generated quite a large set of smaller fixes for potential crashes and
> missed error handling.

Pulled now.  Thanks.


> ----------------------------------------------------------------
> 
> Should probably have pointed out that the DaVinci runtime PM fix here is
> a big diff but mostly code motion, it fixes problems where the device
> would stop working after runtime PM.

OK, will mention in the pull request to Linus.


Takashi

  reply	other threads:[~2019-01-18 15:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-18 12:54 [GIT PULL] ASoC fixes for v5.0 Mark Brown
2019-01-18 15:09 ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-08 12:34 Mark Brown
2019-02-08 13:15 ` Takashi Iwai
2019-02-19 11:18 Mark Brown
2019-02-19 12:38 ` Takashi Iwai

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=s5hfttq0zq9.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    /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