From: Sasha Levin <sashal@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Stable RC build failures (v4.19.y, v5.4.y, v5.5.y)
Date: Wed, 15 Apr 2020 23:41:34 -0400 [thread overview]
Message-ID: <20200416034133.GI1068@sasha-vm> (raw)
In-Reply-To: <20200415183655.GA66707@roeck-us.net>
On Wed, Apr 15, 2020 at 11:36:55AM -0700, Guenter Roeck wrote:
>Hi,
>
>The folloewing build failures currently observed with stable release
>candidates.
>
>Thanks,
>Guenter
>
>---
>v4.19.y:
>
>drivers/gpu/drm/etnaviv/etnaviv_perfmon.c:392:14: error: 'chipFeatures_PIPE_3D' undeclared here
>drivers/gpu/drm/etnaviv/etnaviv_perfmon.c:397:14: error: 'chipFeatures_PIPE_2D'
>drivers/gpu/drm/etnaviv/etnaviv_perfmon.c:402:14: error: 'chipFeatures_PIPE_VG' undeclared here
>
>Culprit is 'drm/etnaviv: rework perfmon query infrastructure'. Applying
>commit 15ff4a7b5841 ("etnaviv: perfmon: fix total and idle HI cyleces
>readout") as well fixes the problem.
Done.
>v5.4.y, v5.5.y:
>
>drivers/mmc/host/sdhci-tegra.c: In function 'tegra_sdhci_set_timeout':
>drivers/mmc/host/sdhci-tegra.c:1256:2: error:
> implicit declaration of function '__sdhci_set_timeout'
>
>Culprit is "sdhci: tegra: Implement Tegra specific set_timeout callback".
>__sdhci_set_timeout() was introduced with commit 7d76ed77cfbd3 ("mmc:
>sdhci: Refactor sdhci_set_timeout()"). Unfortunately, applying that patch
>results in a conflict.
But that patch can be resolved by grabbing 7907ebe741a7 ("mmc: sdhci:
Convert sdhci_set_timeout_irq() to non-static") which just makes
__sdhci_set_timeout() non-static.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-04-16 3:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 18:36 Stable RC build failures (v4.19.y, v5.4.y, v5.5.y) Guenter Roeck
2020-04-16 3:41 ` Sasha Levin [this message]
2020-04-16 4:38 ` Guenter Roeck
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=20200416034133.GI1068@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.org \
/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