From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Anshuman Gupta <anshuman.gupta@intel.com>
Cc: igt-dev@lists.freedesktop.org, chris.p.wilson@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t v2 1/2] lib: Add silent __igt_i915_driver_unload
Date: Tue, 15 Feb 2022 14:29:01 -0800 [thread overview]
Message-ID: <87mtirdas2.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20220215141053.27928-2-anshuman.gupta@intel.com>
On Tue, 15 Feb 2022 06:10:52 -0800, Anshuman Gupta wrote:
>
> Add silent __igt_i915_driver_unload(), which will not
> print any warning in case of passed argument is NULL.
> This will be used by some igt test, which marks i915
> module busy and expect i915 module unload to fail.
> These tests requires a silent lib function to unload
> the i915 module correctly.
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> v2:
> - Change commit log. [Ashutosh]
> - Change whom to who. [Ashutosh]
> - When aux audule unload fails mark who with module name. [Ashutosh]
> - Keep same type of return type in
> __igt_i915_driver_unload(). [Ashutosh]
>
> Cc: Chris Wilson <chris.p.wilson@intel.com>
> Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
next prev parent reply other threads:[~2022-02-15 22:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 14:10 [igt-dev] [PATCH i-g-t v2 0/2] Nuke unload_i915 Anshuman Gupta
2022-02-15 14:10 ` [igt-dev] [PATCH i-g-t v2 1/2] lib: Add silent __igt_i915_driver_unload Anshuman Gupta
2022-02-15 22:29 ` Dixit, Ashutosh [this message]
2022-02-15 14:10 ` [igt-dev] [PATCH i-g-t v2 2/2] perf/perf_pmu: Nuke unload_i915 Anshuman Gupta
2022-02-15 22:29 ` Dixit, Ashutosh
2022-02-15 19:53 ` [igt-dev] ✓ Fi.CI.BAT: success for Nuke unload_i915 (rev2) Patchwork
2022-02-15 23:31 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=87mtirdas2.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=chris.p.wilson@intel.com \
--cc=igt-dev@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