From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org,
Sagar Arun Kamble <sagar.a.kamble@intel.com>
Subject: Re: [PATCH v6 1/3] drm/i915: Add Guc/HuC firmware details to error state
Date: Wed, 08 Nov 2017 13:27:20 +0200 [thread overview]
Message-ID: <1510140440.4626.4.camel@linux.intel.com> (raw)
In-Reply-To: <150997772717.17627.11455623992578279647@mail.alporthouse.com>
On Mon, 2017-11-06 at 14:15 +0000, Chris Wilson wrote:
> Quoting Michal Wajdeczko (2017-10-26 18:36:55)
> > Include GuC and HuC firmware details in captured error state
> > to provide additional debug information. To reuse existing
> > uc firmware pretty printer, introduce new drm-printer variant
> > that works with our i915_error_state_buf output. Also update
> > uc firmware pretty printer to accept const input.
> >
> > v2: don't rely on current caps (Chris)
> > dump correct fw info (Michal)
> > v3: simplify capture of custom paths (Chris)
> > v4: improve 'why' comment (Joonas)
> > trim output if no fw path (Michal)
> > group code around uc error state (Michal)
> > v5: use error in cleanup_uc (Michal)
> >
> > Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
<SNIP>
>
> Removed the chunk and applied.
So, this got merged. What's is the next series to look forward to? I
again see multiple GuC series in my inbox and mailing list.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-08 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 17:36 [PATCH v6 1/3] drm/i915: Add Guc/HuC firmware details to error state Michal Wajdeczko
2017-10-26 17:36 ` [PATCH v6 2/3] drm/i915: Make GuC log part of the uC " Michal Wajdeczko
2017-10-26 17:36 ` [PATCH v6 3/3] drm/i915: Handle error-state modparams in dedicated functions Michal Wajdeczko
2017-10-26 18:01 ` ✓ Fi.CI.BAT: success for series starting with [v6,1/3] drm/i915: Add Guc/HuC firmware details to error state Patchwork
2017-10-26 19:10 ` ✓ Fi.CI.IGT: " Patchwork
2017-11-06 14:15 ` [PATCH v6 1/3] " Chris Wilson
2017-11-08 11:27 ` Joonas Lahtinen [this message]
2017-11-08 12:20 ` Michal Wajdeczko
2017-11-08 20:21 ` Michal Wajdeczko
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=1510140440.4626.4.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
--cc=sagar.a.kamble@intel.com \
/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