public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: achill@achill.org, akpm@linux-foundation.org, broonie@kernel.org,
	conor@kernel.org, f.fainelli@gmail.com, hargar@microsoft.com,
	jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
	linux@roeck-us.net, lkft-triage@lists.linaro.org,
	patches@kernelci.org, patches@lists.linux.dev,
	pavel@nabladev.com, rwarsow@gmx.de, shuah@kernel.org,
	sr@sladewatkins.com, stable@vger.kernel.org,
	sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org,
	Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH 6.19 000/342] 6.19.11-rc1 review
Date: Thu,  2 Apr 2026 14:04:12 +0200	[thread overview]
Message-ID: <20260402120412.116239-1-ojeda@kernel.org> (raw)
In-Reply-To: <20260331161758.909578033@linuxfoundation.org>

On Tue, 31 Mar 2026 18:17:13 +0200 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.19.11 release.
> There are 342 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, 02 Apr 2026 16:16:56 +0000.
> Anything received after that time might be too late.

Boot-tested under QEMU for Rust x86_64, arm64 and riscv64; built-tested
for loongarch64 and arm32:

Tested-by: Miguel Ojeda <ojeda@kernel.org>

Thanks!

Cheers,
Miguel

      parent reply	other threads:[~2026-04-02 12:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 16:17 [PATCH 6.19 000/342] 6.19.11-rc1 review Greg Kroah-Hartman
2026-03-31 17:23 ` Ronald Warsow
2026-03-31 18:24 ` Dileep malepu
2026-03-31 21:18 ` François Valenduc
2026-04-01 18:20   ` François Valenduc
     [not found]     ` <2026040220-sincere-undaunted-65b5@gregkh>
     [not found]       ` <CACU-xRtcWU=RKOfhL+8B2YmYnPN-fxc+TYc4rjaQEFc5qAk1+g@mail.gmail.com>
     [not found]         ` <2026040243-dwelled-overdrive-51b3@gregkh>
2026-04-02 19:09           ` François Valenduc
2026-04-03  6:15             ` Greg Kroah-Hartman
2026-04-02  7:56   ` Thorsten Leemhuis
2026-03-31 21:52 ` Justin Forbes
2026-03-31 22:18 ` Florian Fainelli
2026-04-01 11:42   ` Greg Kroah-Hartman
2026-04-01  6:21 ` Peter Schneider
2026-04-01  6:45 ` Shung-Hsi Yu
2026-04-01  7:28 ` Brett A C Sheffield
2026-04-01  9:17 ` Ron Economos
2026-04-01  9:19 ` Jon Hunter
2026-04-01 10:06   ` Luna Jernberg
2026-04-01 11:14 ` Takeshi Ogasawara
2026-04-01 15:58 ` Jeffrin Thalakkottoor
2026-04-01 16:09 ` Shuah Khan
2026-04-01 17:35 ` Mark Brown
2026-04-02  9:43 ` Barry K. Nathan
2026-04-02 12:04 ` Miguel Ojeda [this message]

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=20260402120412.116239-1-ojeda@kernel.org \
    --to=ojeda@kernel.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --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@nabladev.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --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