From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Lionel Landwerlin <lionel.g.landwerlin@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Show machine type in error state
Date: Thu, 03 Jan 2019 14:29:20 +0200 [thread overview]
Message-ID: <87ef9t53hb.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <154651239954.27300.14111389164901789640@skylake-alporthouse-com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quoting Lionel Landwerlin (2019-01-03 10:42:22)
>> On 03/01/2019 10:12, Chris Wilson wrote:
>> > As the question of 32b/64b kernels became relevant in the light of
>> > certain bugs, include that information in the error state.
>> >
>> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>> > Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>>
>>
>> I was thinking about it, thanks for doing this.
>>
>> Not sure about the content of the machine field though.
>
> uname -m
> i386 or x86_64 iirc.
Yes, it shows 'x86_64'. But I am too late in here =)
-Mika
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-03 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 10:12 [PATCH] drm/i915: Show machine type in error state Chris Wilson
2019-01-03 10:42 ` Lionel Landwerlin
2019-01-03 10:46 ` Chris Wilson
2019-01-03 11:48 ` Lionel Landwerlin
2019-01-03 12:29 ` Mika Kuoppala [this message]
2019-01-03 11:08 ` ✗ Fi.CI.BAT: failure for " 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=87ef9t53hb.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@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 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.