From: ChromeOS Kernel Stable Merge <mdb.chromeos-kernel-auto-merge+noreply@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, chromeos-kernel-stable-merge@google.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.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, conor@kernel.org, allen.lkml@gmail.com,
broonie@kernel.org
Subject: Re: [PATCH 6.1 00/86] 6.1.104-rc2 review
Date: Thu, 08 Aug 2024 13:35:45 +0000 [thread overview]
Message-ID: <0000000000009f2a72061f2c1aff@google.com> (raw)
In-Reply-To: <20240808091131.014292134@linuxfoundation.org>
Hello,
This rc kernel passed ChromeOS CQ tests:
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/5766148/2?tab=checks
Thanks,
Tested-by: ChromeOS CQ Test <chromeos-kernel-stable-merge@google.com>
next prev parent reply other threads:[~2024-08-08 13:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 9:11 [PATCH 6.1 00/86] 6.1.104-rc2 review Greg Kroah-Hartman
2024-08-08 10:33 ` Salvatore Bonaccorso
2024-08-10 5:02 ` Salvatore Bonaccorso
2024-08-10 21:36 ` Quentin Monnet
2024-08-11 15:23 ` Greg Kroah-Hartman
2024-08-08 11:03 ` Miguel Ojeda
2024-08-08 11:55 ` Ron Economos
2024-08-08 14:43 ` Ron Economos
2024-08-08 16:45 ` Ron Economos
2024-08-11 10:14 ` Greg Kroah-Hartman
2024-08-08 13:35 ` ChromeOS Kernel Stable Merge [this message]
2024-08-08 16:58 ` Pavel Machek
2024-08-08 17:03 ` Anders Roxell
2024-08-09 5:46 ` Peter Schneider
2024-08-09 10:51 ` Jon Hunter
2024-08-09 11:58 ` Shreeya Patel
2024-08-09 18:35 ` Florian Fainelli
2024-08-12 21:49 ` Guenter Roeck
2024-08-13 2:44 ` Guenter Roeck
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=0000000000009f2a72061f2c1aff@google.com \
--to=mdb.chromeos-kernel-auto-merge+noreply@google.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=chromeos-kernel-stable-merge@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.