From: Jani Nikula <jani.nikula@linux.intel.com>
To: Nicholas Mc Guire <der.herr@hofr.at>,
"Saarinen, Jani" <jani.saarinen@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Nicholas Mc Guire <hofrat@osadl.org>
Subject: Re: ??? Fi.CI.BAT: failure for drm/i915: relax uncritical udelay_range() settings
Date: Fri, 16 Dec 2016 11:27:04 +0200 [thread overview]
Message-ID: <87poksns0n.fsf@intel.com> (raw)
In-Reply-To: <20161216074733.GA2774@osadl.at>
On Fri, 16 Dec 2016, Nicholas Mc Guire <der.herr@hofr.at> wrote:
> On Fri, Dec 16, 2016 at 07:29:59AM +0000, Saarinen, Jani wrote:
>> > == Series Details ==
>> >
>> > Series: drm/i915: relax uncritical udelay_range() settings
>> > URL : https://patchwork.freedesktop.org/series/16900/
>> > State : failure
>> >
>> > == Summary ==
>> >
>> > Series 16900v1 drm/i915: relax uncritical udelay_range() settings
>> > https://patchwork.freedesktop.org/api/1.0/series/16900/revisions/1/mbox/
>> >
>> > Test gem_ringfill:
>> > Subgroup basic-default-hang:
>> > pass -> INCOMPLETE (fi-hsw-4770)
>> running: igt/gem_ringfill/basic-default-hang
>> [117/247] skip: 8, pass: 109 /
>> Build timed out (after 17 minutes). Marking the build as aborted.
>>
> This might be a conflict caused by the initial patch which was discssed
> and then after agreeing that rather than moving to udelay() usleep:range
> with som adjustments would be the right way to go.
> are both patches queued now ?
>
> I think I caused the problem by changing the subject line of the patch
> while adding a V2 - because the original subject line was no longer corrct
> (it noted udely) - the V2 patch is marked as "rev 1" in patchwork though.
>
> not quite clear - anyway sorry if I made some sort of a mess here
> the patch applies cleanly on next-20161216.
Nah, some other hickup in CI on a machine that's not affected by your
change.
Pushed to drm-intel-next-queued, thanks for the patch.
BR,
Jani.
>
> thx!
> hofrat
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-12-16 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 1:59 [PATCH V2] drm/i915: relax uncritical udelay_range() settings Nicholas Mc Guire
2016-12-16 2:52 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-12-16 7:29 ` Saarinen, Jani
2016-12-16 7:47 ` ??? " Nicholas Mc Guire
2016-12-16 9:27 ` Jani Nikula [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=87poksns0n.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=der.herr@hofr.at \
--cc=hofrat@osadl.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.saarinen@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