From: Lucas De Marchi <lucas.demarchi@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [CI] HAX: drm/i915: Add softdep
Date: Fri, 15 Apr 2022 17:31:59 -0700 [thread overview]
Message-ID: <20220416003159.cjlmcbevmmxus2td@ldmartin-desk2> (raw)
In-Reply-To: <20220415215640.2177403-1-lucas.demarchi@intel.com>
On Fri, Apr 15, 2022 at 02:56:40PM -0700, Lucas De Marchi wrote:
>CI is having several issues due to unbinding i915 while the sound driver
>is still doing something. It's particularly harmful when it's not idle
>and we attempt to remove i915.
>
>We still need to fix the snd driver so we can more reliably remove i915,
>but this can't block other i915 tests. By adding a post softdep we make sure
>that on module removal, kmod first removes snd_hda_intel, and only after
>that removes i915.
>
>Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
ignore, it broke other platforms.
Lucas De Marchi
prev parent reply other threads:[~2022-04-16 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 21:56 [Intel-gfx] [CI] HAX: drm/i915: Add softdep Lucas De Marchi
2022-04-15 22:23 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-04-15 22:47 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-04-16 0:31 ` Lucas De Marchi [this message]
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=20220416003159.cjlmcbevmmxus2td@ldmartin-desk2 \
--to=lucas.demarchi@intel.com \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox