From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [ALSA] 1a414f48d7: WARNING: CPU: 0 PID: 252 at sound/hda/hdac_i915.c:129 pin2port+0x2a/0x40 [snd_hda_core]()
Date: Wed, 16 Mar 2016 15:57:02 +0800 [thread overview]
Message-ID: <87io0msvn5.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <s5h37rqx4me.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
Takashi Iwai <tiwai@suse.de> writes:
> On Wed, 16 Mar 2016 01:23:15 +0100,
> kernel test robot wrote:
>>
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> commit 1a414f48d7ccb197b61c18888b72327c98171844 ("ALSA: hda - Add a
>> sanity check of pin / port mapping on i915 HDMI/DP")
>
> The question is rather which hardware you're testing.
> Is it a pre-Haswell hardware?
Yes. It is a pre-Haswell machine.
> If yes, it should be already covered by
> the patch I queued yesterday, so today's tree should work fine.
> So, let me know if this is still seen with the upcoming tree.
Sure.
Best Regards,
Huang, Ying
WARNING: multiple messages have this Message-ID (diff)
From: "Huang\, Ying" <ying.huang@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: <lkp@01.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [lkp] [ALSA] 1a414f48d7: WARNING: CPU: 0 PID: 252 at sound/hda/hdac_i915.c:129 pin2port+0x2a/0x40 [snd_hda_core]()
Date: Wed, 16 Mar 2016 15:57:02 +0800 [thread overview]
Message-ID: <87io0msvn5.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <s5h37rqx4me.wl-tiwai@suse.de> (Takashi Iwai's message of "Wed, 16 Mar 2016 08:29:29 +0100")
Takashi Iwai <tiwai@suse.de> writes:
> On Wed, 16 Mar 2016 01:23:15 +0100,
> kernel test robot wrote:
>>
>> FYI, we noticed the below changes on
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> commit 1a414f48d7ccb197b61c18888b72327c98171844 ("ALSA: hda - Add a
>> sanity check of pin / port mapping on i915 HDMI/DP")
>
> The question is rather which hardware you're testing.
> Is it a pre-Haswell hardware?
Yes. It is a pre-Haswell machine.
> If yes, it should be already covered by
> the patch I queued yesterday, so today's tree should work fine.
> So, let me know if this is still seen with the upcoming tree.
Sure.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2016-03-16 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 0:23 [ALSA] 1a414f48d7: WARNING: CPU: 0 PID: 252 at sound/hda/hdac_i915.c:129 pin2port+0x2a/0x40 [snd_hda_core]() kernel test robot
2016-03-16 0:23 ` [lkp] " kernel test robot
2016-03-16 7:29 ` Takashi Iwai
2016-03-16 7:29 ` [lkp] " Takashi Iwai
2016-03-16 7:57 ` Huang, Ying [this message]
2016-03-16 7:57 ` [LKP] " Huang, Ying
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=87io0msvn5.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.