From: Mark Brown <broonie@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: kernel-build-reports@lists.linaro.org,
nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Jonathan Hunter <jonathanh@nvidia.com>,
Ben Skeggs <bskeggs@redhat.com>,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: next/master boot: 142 boots: 2 failed, 130 passed with 7 offline, 3 conflicts (next-20181129)
Date: Thu, 29 Nov 2018 11:57:19 +0000 [thread overview]
Message-ID: <20181129115719.GE10570@sirena.org.uk> (raw)
In-Reply-To: <20181129115413.GA28224@ulmo>
[-- Attachment #1.1: Type: text/plain, Size: 344 bytes --]
On Thu, Nov 29, 2018 at 12:54:13PM +0100, Thierry Reding wrote:
> This looks like the same issue that I was seeing a couple of weeks ago.
> There's a fix for this here:
> http://patchwork.ozlabs.org/patch/993812/
> Not sure if Ben's picked that up yet, though.
It's certainly not visible in -next and the issue is showing so guessing
not.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-11-29 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5bffcc4f.1c69fb81.ee2e8.b541@mx.google.com>
2018-11-29 11:44 ` next/master boot: 142 boots: 2 failed, 130 passed with 7 offline, 3 conflicts (next-20181129) Mark Brown
[not found] ` <20181129114413.GC10570-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2018-11-29 11:54 ` Thierry Reding
2018-11-29 11:57 ` Mark Brown [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=20181129115719.GE10570@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=thierry.reding@gmail.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.