From: Guenter Roeck <linux@roeck-us.net>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Eric Anholt <eric@anholt.net>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
David Airlie <airlied@linux.ie>,
rjw@rjwysocki.net
Subject: Re: [PATCH] drm/vc4: Remove broken attempt at GPU reset using genpd.
Date: Fri, 22 Jan 2016 09:06:05 -0800 [thread overview]
Message-ID: <56A2617D.9030200@roeck-us.net> (raw)
In-Reply-To: <56A25EDD.7010409@gmail.com>
On 01/22/2016 08:54 AM, Sudip Mukherjee wrote:
> On Friday 22 January 2016 08:01 PM, Guenter Roeck wrote:
>> On Mon, Dec 21, 2015 at 06:08:44PM -0800, Eric Anholt wrote:
>>> I've tested and confirmed that it doesn't actually work. We'll need
>>> to sort out how to do this properly later, but for now just remove it
>>> since it also caused build breakage due to using CONFIG_PM_SLEEP
>>> functions without our Kconfig depending on PM_SLEEP.
>>>
>>> Signed-off-by: Eric Anholt <eric@anholt.net>
>>
>> Still broken upstream.
>
> I saw Eric sending a pull request for it. But it was never pulled, maybe for the subject.
> Looks like rc1 will be broken for many arch.
>
Could be worse. Essentially every allmodconfig/allyesconfig which doesn't configure pm
is affected.
With my tests (v4.4-10282-geae2177):
Build results:
total: 146 pass: 142 fail: 4
Failed builds:
alpha:allmodconfig
m68k:allmodconfig
parisc:allmodconfig
xtensa:allmodconfig
Qemu test results:
total: 96 pass: 94 fail: 2
Failed tests:
arm64:smp:defconfig
arm64:nosmp:defconfig
arm64 qemu tests are broken for a different reason. There is a patch to fix it,
but for some reason it didn't make it into mainline (yet). It is in -next, though.
Guenter
prev parent reply other threads:[~2016-01-22 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 2:08 [PATCH] drm/vc4: Remove broken attempt at GPU reset using genpd Eric Anholt
2015-12-22 2:08 ` Eric Anholt
2015-12-22 4:43 ` Sudip Mukherjee
2015-12-22 4:43 ` Sudip Mukherjee
2016-01-01 4:56 ` Sudip Mukherjee
2016-01-01 4:56 ` Sudip Mukherjee
2016-01-22 14:31 ` Guenter Roeck
2016-01-22 16:54 ` Sudip Mukherjee
2016-01-22 16:54 ` Sudip Mukherjee
2016-01-22 17:06 ` Guenter Roeck [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=56A2617D.9030200@roeck-us.net \
--to=linux@roeck-us.net \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sudipm.mukherjee@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.