<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - [BAT][KBL] Warning at block/blk-mq.c:2667 blk_mq_update_nr_hw_queues+0x118/0x120 in CI" href="https://bugs.freedesktop.org/show_bug.cgi?id=101022#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - [BAT][KBL] Warning at block/blk-mq.c:2667 blk_mq_update_nr_hw_queues+0x118/0x120 in CI" href="https://bugs.freedesktop.org/show_bug.cgi?id=101022">bug 101022</a> from <a class="email" href="mailto:krisman@collabora.co.uk" title="krisman@collabora.co.uk">krisman@collabora.co.uk</a> <pre>(In reply to Martin Peres from <a href="show_bug.cgi?id=101022#c7">comment #7</a>) > (In reply to krisman from <a href="show_bug.cgi?id=101022#c6">comment #6</a>) > > (In reply to krisman from <a href="show_bug.cgi?id=101022#c5">comment #5</a>) > > > Keith suggested the following patch > > > > After running on the CI, I confirmed the patch fixes the issue. It has been > > queued in Jen's tree for the next -rc: > > > > <a href="https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/">https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/</a> > > ?h=for-linus&id=e4dc2b32df5573b077f6723e01cf761d236d5113 > > > > The CI run: > > > > <a href="https://intel-gfx-ci.01.org/CI/Trybot_861/fi-kbl-7500u/">https://intel-gfx-ci.01.org/CI/Trybot_861/fi-kbl-7500u/</a> > > igt@<a href="mailto:kms_pipe_crc_basic@suspend-read-crc-pipe-a.html">kms_pipe_crc_basic@suspend-read-crc-pipe-a.html</a> > > You rock! We can merge it into the for-CI branch, so as we don't have to > wait for the backmerge to get it back :) What is the process for that? Is there a different list for submitting it?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>