From: Guenter Roeck <linux@roeck-us.net>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@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
Subject: Re: [PATCH 5.13 0/2] 5.13.1-rc1 review
Date: Mon, 5 Jul 2021 13:40:20 -0700 [thread overview]
Message-ID: <20210705204020.GD3118687@roeck-us.net> (raw)
In-Reply-To: <20210705105656.1512997-1-sashal@kernel.org>
On Mon, Jul 05, 2021 at 06:56:54AM -0400, Sasha Levin wrote:
>
> This is the start of the stable review cycle for the 5.13.1 release.
> There are 2 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 07 Jul 2021 10:49:46 AM UTC.
> Anything received after that time might be too late.
>
Build results:
total: 151 pass: 151 fail: 0
Qemu test results:
total: 462 pass: 462 fail: 0
Tested-by: Guenter Roeck <linux@roeck-us.net>
Guenter
next prev parent reply other threads:[~2021-07-05 20:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 10:56 [PATCH 5.13 0/2] 5.13.1-rc1 review Sasha Levin
2021-07-05 10:56 ` [PATCH 5.13 1/2] Revert "KVM: x86/mmu: Drop kvm_mmu_extended_role.cr4_la57 hack" Sasha Levin
2021-07-05 10:56 ` [PATCH 5.13 2/2] Linux 5.13.1-rc1 Sasha Levin
2021-07-05 12:13 ` [PATCH 5.13 0/2] 5.13.1-rc1 review Thomas Backlund
2021-07-05 12:41 ` Greg KH
2021-07-05 18:46 ` Fox Chen
2021-07-07 12:22 ` Sasha Levin
2021-07-05 20:40 ` Guenter Roeck [this message]
2021-07-07 12:25 ` Sasha Levin
2021-07-06 4:49 ` Naresh Kamboju
2021-07-07 12:25 ` Sasha Levin
2021-07-06 22:43 ` Shuah Khan
2021-07-07 12:26 ` Sasha Levin
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=20210705204020.GD3118687@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=sashal@kernel.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