From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "Hiler, Arkadiusz" <arkadiusz.hiler@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Peres, Martin" <martin.peres@intel.com>,
"Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.DOCS: warning for Consider DBuf bandwidth when calculating CDCLK (rev2)
Date: Wed, 18 Mar 2020 08:43:29 +0000 [thread overview]
Message-ID: <92f06a328dc947b49c8f7c4cfedaa32d@intel.com> (raw)
In-Reply-To: <20200318083307.lnnhoalkltvfv4l6@ahiler-desk1.fi.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1131 bytes --]
Wonder, how we end up merging _stuff_ with failed IGT and loads of warnings..
https://patchwork.freedesktop.org/series/74738/
... while I get beaten for each and every single warning in my patches 😊
Best Regards,
Lisovskiy Stanislav
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
________________________________
From: Hiler, Arkadiusz
Sent: Wednesday, March 18, 2020 10:33:07 AM
To: Lisovskiy, Stanislav
Cc: intel-gfx@lists.freedesktop.org; Peres, Martin; Vudum, Lakshminarayana
Subject: Re: ✗ Fi.CI.DOCS: warning for Consider DBuf bandwidth when calculating CDCLK (rev2)
On Tue, Mar 17, 2020 at 12:43:40PM +0200, Lisovskiy, Stanislav wrote:
> What is this weird DOC warning about? "Error: Cannot open file ./drivers/gpu/
> drm/i915/i915_gem_fence_reg.c"
>
> - wondering, how is that related to this patch.
Looks like you were unlucky and your series got tested with this merged:
https://patchwork.freedesktop.org/series/74738/
but before the fix has landed:
https://patchwork.freedesktop.org/series/74778/
It's all clean now.
--
Cheers,
Arek
[-- Attachment #1.2: Type: text/html, Size: 2783 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-03-18 8:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 11:37 [Intel-gfx] [PATCH v1 0/3] Consider DBuf bandwidth when calculating CDCLK Stanislav Lisovskiy
2020-03-16 11:37 ` [Intel-gfx] [PATCH v1 1/3] drm/i915: Decouple cdclk calculation from modeset checks Stanislav Lisovskiy
2020-03-16 23:36 ` Manasi Navare
2020-03-17 13:21 ` Ville Syrjälä
2020-03-16 11:37 ` [Intel-gfx] [PATCH v1 2/3] drm/i915: Adjust CDCLK accordingly to our DBuf bw needs Stanislav Lisovskiy
2020-03-16 22:43 ` [Intel-gfx] [PATCH v2 " Stanislav Lisovskiy
2020-03-17 13:46 ` Ville Syrjälä
2020-03-17 14:40 ` Lisovskiy, Stanislav
2020-03-16 11:37 ` [Intel-gfx] [PATCH v1 3/3] drm/i915: Remove unneeded hack now for CDCLK Stanislav Lisovskiy
2020-03-16 23:51 ` Manasi Navare
2020-03-16 20:06 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Consider DBuf bandwidth when calculating CDCLK Patchwork
2020-03-16 20:34 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-03-17 0:36 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for Consider DBuf bandwidth when calculating CDCLK (rev2) Patchwork
2020-03-17 10:43 ` Lisovskiy, Stanislav
2020-03-18 8:33 ` Arkadiusz Hiler
2020-03-18 8:43 ` Lisovskiy, Stanislav [this message]
2020-03-18 8:55 ` Arkadiusz Hiler
2020-03-18 9:00 ` Lisovskiy, Stanislav
2020-03-17 0:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-03-17 9:26 ` [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=92f06a328dc947b49c8f7c4cfedaa32d@intel.com \
--to=stanislav.lisovskiy@intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lakshminarayana.vudum@intel.com \
--cc=martin.peres@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.