<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [BXT/KBL] - HDMI - HD audio passthrough dont work" href="https://bugs.freedesktop.org/show_bug.cgi?id=98797#c129">Comment # 129</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [BXT/KBL] - HDMI - HD audio passthrough dont work" href="https://bugs.freedesktop.org/show_bug.cgi?id=98797">bug 98797</a> from <a class="email" href="mailto:jani.nikula@intel.com" title="Jani Nikula <jani.nikula@intel.com>"> Jani Nikula</a> <pre>(In reply to Jani Nikula from <a href="show_bug.cgi?id=98797#c128">comment #128</a>) > As to the other and remaining issues such as ones reported by Peter in > <a href="show_bug.cgi?id=98797#c124">comment #124</a>, please file fresh reports for them, one bug per issue. Please > cite this bug if the issues are related to HBR audio. Please mention LSPCON > if it's related to LSPCON. For background, should anyone care, any developer starting to read a 125+ comment bug report with all the detours and conflated issues and out-of-office autoreplies is going to get discouraged and demotivated off the bat. If the first description of a new bug report is good, we can get straight at the problem from the start.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>