From: Rudi Heitbaum <rudi@heitbaum.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 6.1 000/193] 6.1.8-rc1 review
Date: Mon, 23 Jan 2023 07:42:18 +0000 [thread overview]
Message-ID: <20230123074218.GA219043@939e86c225aa> (raw)
In-Reply-To: <20230122150246.321043584@linuxfoundation.org>
On Sun, Jan 22, 2023 at 04:02:09PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.8 release.
> There are 193 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.
Hi Greg,
6.1.8-rc1 tested.
Run tested on:
- Allwinner H6 (Tanix TX6)
- Intel Alder Lake x86_64 (nuc12 i7-1260P)
In addition - build tested for:
- Allwinner A64
- Allwinner H3
- Allwinner H5
- NXP iMX6
- NXP iMX8
- Qualcomm Dragonboard
- Rockchip RK3288
- Rockchip RK3328
- Rockchip RK3399pro
- Samsung Exynos
Tested-by: Rudi Heitbaum <rudi@heitbaum.com>
--
Rudi
next prev parent reply other threads:[~2023-01-23 7:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 15:02 [PATCH 6.1 000/193] 6.1.8-rc1 review Greg Kroah-Hartman
2023-01-22 15:02 ` [PATCH 6.1 021/193] x86/asm: Fix an assembler warning with current binutils Greg Kroah-Hartman
2023-01-22 22:54 ` [PATCH 6.1 000/193] 6.1.8-rc1 review ogasawara takeshi
2023-01-23 4:09 ` Joel Fernandes
2023-01-23 7:42 ` Rudi Heitbaum [this message]
2023-01-23 8:03 ` Conor Dooley
2023-01-23 8:09 ` Naresh Kamboju
2023-01-23 19:11 ` Tom Saeger
2023-01-23 19:42 ` Tom Saeger
2023-01-24 12:11 ` Naresh Kamboju
2023-01-24 12:54 ` Tom Saeger
2023-01-24 15:57 ` Naresh Kamboju
2023-01-24 11:48 ` Naresh Kamboju
2023-01-23 9:03 ` Bagas Sanjaya
2023-01-23 9:07 ` Ron Economos
2023-01-23 11:15 ` Sudip Mukherjee
-- strict thread matches above, loose matches on Subject: below --
2023-01-22 19:38 Ronald Warsow
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=20230123074218.GA219043@939e86c225aa \
--to=rudi@heitbaum.com \
--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=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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