LKML Archive on 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, lkft-triage@lists.linaro.org,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	stable@vger.kernel.org
Subject: Re: [PATCH 5.13 000/224] 5.13.6-rc2 review
Date: Tue, 27 Jul 2021 11:08:13 -0700	[thread overview]
Message-ID: <20210727180813.GG1721083@roeck-us.net> (raw)
In-Reply-To: <20210726165238.919699741@linuxfoundation.org>

On Tue, Jul 27, 2021 at 07:06:12AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.13.6 release.
> There are 224 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 Wed, 28 Jul 2021 16:52:07 +0000.
> Anything received after that time might be too late.
> 

Build results:
	total: 154 pass: 154 fail: 0
Qemu test results:
	total: 471 pass: 471 fail: 0

Note: The previously reported build error
	cc1: error: '9880' is not a valid offset in '-mstack-protector-guard-offset='
with riscv:allmodconfig has not been fixed, but it looks like I was the
only one affected by this problem, it has become a disctraction, and it
may hide other issues. I disabled CONFIG_GCC_PLUGIN_RANDSTRUCT in my riscv
test builds to avoid the build failure, and will no longer report it.

Tested-by: Guenter Roeck <linux@roeck-us.net>

Guenter

  parent reply	other threads:[~2021-07-27 18:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  5:06 Greg Kroah-Hartman
2021-07-27  7:15 ` Naresh Kamboju
2021-07-27 18:08 ` Guenter Roeck [this message]
2021-07-27 18:28 ` Florian Fainelli

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=20210727180813.GG1721083@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=pavel@denx.de \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [PATCH 5.13 000/224] 5.13.6-rc2 review' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).