All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, 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/169] 5.4.25-rc4 review
Date: Wed, 11 Mar 2020 16:06:53 -0700	[thread overview]
Message-ID: <20200311230653.GA25697@roeck-us.net> (raw)
In-Reply-To: <20200311204002.240698596@linuxfoundation.org>

On Wed, Mar 11, 2020 at 09:41:16PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.25 release.
> There are 169 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 Fri, 13 Mar 2020 20:39:27 +0000.
> Anything received after that time might be too late.
> 

Build results:
	total: 158 pass: 146 fail: 12
Failed builds:
	alpha:allmodconfig
	arm:allmodconfig
	arm64:allmodconfig
	m68k:allmodconfig
	mips:allmodconfig
	nds32:allmodconfig
	parisc:allmodconfig
	powerpc:allmodconfig
	riscv:defconfig
	s390:allmodconfig
	sparc64:allmodconfig
	xtensa:allmodconfig
Qemu test results:
	total: 422 pass: 405 fail: 17
Failed tests:
	<all riscv>

As already reported, the failure is:

drivers/gpu/drm/virtio/virtgpu_object.c:31:67: error: expected ')' before 'int'
   31 | module_param_named(virglhack, virtio_gpu_virglrenderer_workaround, int, 0400);

Guenter

  parent reply	other threads:[~2020-03-11 23:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 20:41 [PATCH 5.4 000/169] 5.4.25-rc4 review Greg Kroah-Hartman
2020-03-11 22:06 ` Guenter Roeck
2020-03-12  7:02   ` Greg Kroah-Hartman
2020-03-11 23:06 ` Guenter Roeck [this message]
2020-03-11 23:22   ` Thomas Backlund
2020-03-12  7:02     ` Greg Kroah-Hartman

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=20200311230653.GA25697@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 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.