From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [Intel-gfx] [PATCH 1/1] drm/i915/guc: Update to GuC version 70.1.1 #forregzbot
Date: Thu, 21 Jul 2022 14:51:44 +0200 [thread overview]
Message-ID: <bc32d126-fb34-26d7-0818-a607629c5611@leemhuis.info> (raw)
In-Reply-To: <163e8e23-467a-4b9f-6288-aa850e5c2fc7@leemhuis.info>
On 17.07.22 17:33, Thorsten Leemhuis wrote:
>
>
> On 15.07.22 11:04, Thorsten Leemhuis wrote:
>> On 15.07.22 10:34, Thorsten Leemhuis wrote:
>>> [TLDR: I'm adding this regression report to the list of tracked
>>> regressions; all text from me you find below is based on a few templates
>>> paragraphs you might have encountered already already in similar form.]
>>> [...]> #regzbot ^introduced 2584b3549f4c4081
>>> #regzbot title
>>
>> One more time with more love:
>>
>> #regzbot title drm: i915: support for ADL-P GPUs requires updates GuC
>> firmware files
>
> #regzbot monitor
> https://lore.kernel.org/all/20220715225451.1294354-1-daniele.ceraolospurio@intel.com/
> #regzbot ignore-activity
#regzbot monitor:
https://lore.kernel.org/dri-devel/20220718230732.1409641-1-daniele.ceraolospurio@intel.com/
#regzbot fixed-by: 443148858f26ee0
prev parent reply other threads:[~2022-07-21 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220412225955.1802543-1-John.C.Harrison@Intel.com>
[not found] ` <20220412225955.1802543-2-John.C.Harrison@Intel.com>
[not found] ` <Yli4/8OIbjyRaQAK@mdroper-desk1.amr.corp.intel.com>
[not found] ` <CAPM=9txdca1VnRpp-oNLXpBc2UWq3=ceeim5+Gw4N9tAriRY6A@mail.gmail.com>
2022-07-15 8:34 ` [Intel-gfx] [PATCH 1/1] drm/i915/guc: Update to GuC version 70.1.1 #forregzbot Thorsten Leemhuis
2022-07-15 9:04 ` Thorsten Leemhuis
2022-07-17 15:33 ` Thorsten Leemhuis
2022-07-21 12:51 ` Thorsten Leemhuis [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=bc32d126-fb34-26d7-0818-a607629c5611@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).