From: Takashi Iwai <tiwai@suse.de>
To: Jani Nikula <jani.nikula@intel.com>
Cc: alsa-devel@alsa-project.org, yex.tian@intel.com
Subject: Re: [for-next] NULL pointer dereference in codec probe
Date: Thu, 30 Apr 2015 12:23:22 +0200 [thread overview]
Message-ID: <s5hr3r1ewyt.wl-tiwai@suse.de> (raw)
In-Reply-To: <87fv7i9bgu.fsf@intel.com>
At Thu, 30 Apr 2015 13:06:41 +0300,
Jani Nikula wrote:
>
>
> Hi all, our graphics QA found an issue [1] with the for-next branch of
> [2] merged on top of v4.1-rc1. Backtrace in the bug. I didn't really
> have time to look into the details, but just letting you know.
Looks like the new jack stuff broke something. Keyon, could you take
a look?
thanks,
Takashi
>
> BR,
> Jani.
>
>
> [1] https://bugs.freedesktop.org/show_bug.cgi?id=90229
> [2] git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
>
>
> --
> Jani Nikula, Intel Open Source Technology Center
>
next prev parent reply other threads:[~2015-04-30 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 10:06 [for-next] NULL pointer dereference in codec probe Jani Nikula
2015-04-30 10:23 ` Takashi Iwai [this message]
2015-04-30 11:07 ` Jie, Yang
2015-04-30 12:27 ` Jie, Yang
2015-04-30 13:31 ` Takashi Iwai
2015-04-30 13:53 ` Jie, Yang
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=s5hr3r1ewyt.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=jani.nikula@intel.com \
--cc=yex.tian@intel.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