From: Pavel Machek <pavel@denx.de>
To: Ronald Warsow <rwarsow@gmx.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.13 000/157] 6.13.6-rc1 review
Date: Wed, 5 Mar 2025 20:37:19 +0100 [thread overview]
Message-ID: <Z8in71h4nhXDbbCq@duo.ucw.cz> (raw)
In-Reply-To: <891abe3f-af74-47ee-8f5f-b5d43f11d8fa@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
On Wed 2025-03-05 20:04:26, Ronald Warsow wrote:
> Hi Greg
>
> no regressions here on x86_64 (RKL, Intel 11th Gen. CPU)
>
> Thanks
>
> Tested-by: Ronald Warsow <rwarsow@gmx.de>
>
>
> P.S.
>
> is it necessary to have all cc'ed user informed or should I leave them off ?
Normally, people leave the cc list. It is quite important to keep the
cc list at least for failures, so we can debug them together :-).
BR,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-03-05 19:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 17:47 Greg Kroah-Hartman
2025-03-05 19:04 ` Ronald Warsow
2025-03-05 19:37 ` Pavel Machek [this message]
2025-03-05 20:12 ` Mark Brown
2025-03-06 14:21 ` Greg Kroah-Hartman
2025-03-06 1:11 ` SeongJae Park
2025-03-06 3:43 ` Peter Schneider
2025-03-06 8:03 ` Ron Economos
2025-03-06 12:21 ` Naresh Kamboju
2025-03-06 12:54 ` Takeshi Ogasawara
2025-03-06 15:53 ` Shuah Khan
2025-03-06 16:26 ` Hardik Garg
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=Z8in71h4nhXDbbCq@duo.ucw.cz \
--to=pavel@denx.de \
--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=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®