From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
shuah@kernel.org, patches@kernelci.org,
ben.hutchings@codethink.co.uk, lkft-triage@lists.linaro.org,
stable@vger.kernel.org
Subject: Re: [PATCH 5.4 000/167] 5.4.25-stable review
Date: Tue, 10 Mar 2020 08:55:54 -0700 [thread overview]
Message-ID: <2fc1ae97-cb04-7105-b458-cb456732f48e@roeck-us.net> (raw)
In-Reply-To: <20200310144113.973994620@linuxfoundation.org>
On 3/10/20 7:42 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.25 release.
> There are 167 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Thu, 12 Mar 2020 14:40:27 +0000.
> Anything received after that time might be too late.
>
mips:allmodconfig, nds32:allmodconfig, and probably others:
CC [M] drivers/gpu/drm/virtio/virtgpu_object.o
drivers/gpu/drm/virtio/virtgpu_object.c:31:67: error: expected ')' before 'int'
31 | module_param_named(virglhack, virtio_gpu_virglrenderer_workaround, int, 0400);
Culprit is "drm/virtio: make resource id workaround runtime switchable.".
Upstream commit b0138364da17617d ("drm/virtio: module_param_named() requires linux/moduleparam.h")
is tagged 'Fixes: 3e93bc2a58aa ("drm/virtio: make resource id workaround runtime switchable.")'
and does indeed fix this problem.
When patches are auto-selected for backports, would it be possible to also pick
patches fixing them right away ?
Guenter
next prev parent reply other threads:[~2020-03-10 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 14:42 Greg Kroah-Hartman
2020-03-10 15:19 ` Guenter Roeck
2020-03-10 15:55 ` Guenter Roeck [this message]
2020-03-10 20:08 ` Jon Hunter
2020-03-10 21:16 ` shuah
2020-03-10 22:02 ` 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=2fc1ae97-cb04-7105-b458-cb456732f48e@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®