From: Chris Wilson <chris@chris-wilson.co.uk>
To: Michał Winiarski <michal@hardline.pl>, intel-gfx@lists.freedesktop.org
Cc: Michał Winiarski <michal.winiarski@intel.com>
Subject: Re: [Intel-gfx] [PATCH v3 2/3] drm/i915: Print caller when tainting for CI
Date: Mon, 06 Jul 2020 15:44:05 +0100 [thread overview]
Message-ID: <159404664500.24180.5383440241214822434@build.alporthouse.com> (raw)
In-Reply-To: <20200706144107.204821-2-michal@hardline.pl>
Quoting Michał Winiarski (2020-07-06 15:41:06)
> From: Michał Winiarski <michal.winiarski@intel.com>
>
> We can add taint from multiple places, printing the caller allows us to
> have a better overview of what exactly caused us to do the tainting.
>
> v2: Tweak format and print the device (Chris)
> v3: Move things around (Chris)
>
> Suggested-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Petri Latvala <petri.latvala@intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-07-06 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 14:41 [Intel-gfx] [PATCH v3 1/3] drm/i915: Reboot CI if we get wedged during driver init Michał Winiarski
2020-07-06 14:41 ` [Intel-gfx] [PATCH v3 2/3] drm/i915: Print caller when tainting for CI Michał Winiarski
2020-07-06 14:44 ` Chris Wilson [this message]
2020-07-06 14:41 ` [Intel-gfx] [PATCH v2 3/3] drm/i915: Don't taint when using fault injection Michał Winiarski
2020-07-06 16:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v3,1/3] drm/i915: Reboot CI if we get wedged during driver init Patchwork
2020-07-06 17:03 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-07-06 20:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=159404664500.24180.5383440241214822434@build.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.winiarski@intel.com \
--cc=michal@hardline.pl \
/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.