mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yann Sionneau <ysionneau@kalrayinc.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: 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,
	conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.1 000/141] 6.1.88-rc1 review
Date: Thu, 25 Apr 2024 11:03:03 +0200	[thread overview]
Message-ID: <54706eff-da72-43aa-a91f-e31f0fb972fe@kalrayinc.com> (raw)
In-Reply-To: <20240423213853.356988651@linuxfoundation.org>

Hi Greg,

Le 4/23/24 à 23:37, Greg Kroah-Hartman a écrit :
> This is the start of the stable review cycle for the 6.1.88 release.
> There are 141 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, 25 Apr 2024 21:38:28 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.88-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> and the diffstat can be found below.

I tested 6.1.88-rc1 (cde450ef0f2f5) on Kalray kvx arch (not upstream 
yet) and everything looks good!

It ran on real hw (k200, k200lp and k300 boards), on qemu as well as on 
our internal instruction set simulator (ISS).

Tests were run on several interfaces/drivers (usb, qsfp ethernet, eMMC, 
PCIe endpoint+RC, SPI, remoteproc, uart, iommu). LTP and uClibc-ng 
testsuites are also run without any regression.

Everything looks fine to us.

Tested-by: Yann Sionneau <ysionneau@kalrayinc.com>

-- 
Yann





  parent reply	other threads:[~2024-04-25  9:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 21:37 Greg Kroah-Hartman
2024-04-23 23:00 ` SeongJae Park
2024-04-24  7:21 ` Pavel Machek
2024-04-24  8:23 ` Naresh Kamboju
2024-04-28 12:32   ` Vitaly Chikunov
2024-04-28 16:24     ` Guenter Roeck
2024-04-29 10:21     ` Greg Kroah-Hartman
2024-04-24  8:26 ` Ron Economos
2024-04-24 16:26 ` Florian Fainelli
2024-04-25  9:02 ` Jon Hunter
2024-04-25  9:03 ` Yann Sionneau [this message]
2024-04-25 19:27 ` Mateusz Jończyk
2024-04-25 20:08 ` Shreeya Patel
2024-04-26  2:21 ` Mark Brown
2024-04-26 10:44 ` Pavel Machek

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=54706eff-da72-43aa-a91f-e31f0fb972fe@kalrayinc.com \
    --to=ysionneau@kalrayinc.com \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.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

all inboxes | Powered by JetHome®