From: Hardik Garg <hargar@linux.microsoft.com>
To: gregkh@linuxfoundation.org
Cc: 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@denx.de, rwarsow@gmx.de,
shuah@kernel.org, srw@sladewatkins.net, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 6.12 000/626] 6.12.31-rc1 review
Date: Thu, 29 May 2025 09:29:45 -0700 [thread overview]
Message-ID: <1748536185-5619-1-git-send-email-hargar@linux.microsoft.com> (raw)
In-Reply-To: <20250527162445.028718347@linuxfoundation.org>
The kernel, bpf tool, and perf tool builds fine for v6.12.31-rc1 on x86 and arm64 Azure VM.
Tested-by: Hardik Garg <hargar@linux.microsoft.com>
Thanks,
Hardik
prev parent reply other threads:[~2025-05-29 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 16:18 [PATCH 6.12 000/626] 6.12.31-rc1 review Greg Kroah-Hartman
2025-05-27 16:21 ` [PATCH 6.12 175/626] arm64/mm: Check pmd_table() in pmd_trans_huge() Greg Kroah-Hartman
2025-05-27 16:21 ` [PATCH 6.12 176/626] arm64/mm: Check PUD_TYPE_TABLE in pud_bad() Greg Kroah-Hartman
2025-05-27 18:43 ` [PATCH 6.12 000/626] 6.12.31-rc1 review Florian Fainelli
2025-05-27 22:15 ` Shuah Khan
2025-05-28 0:07 ` Peter Schneider
2025-05-28 0:18 ` Miguel Ojeda
2025-05-28 4:01 ` Harshit Mogalapalli
2025-05-28 6:36 ` Pavel Machek
2025-05-28 9:05 ` Ron Economos
2025-05-28 10:22 ` Naresh Kamboju
2025-05-28 10:51 ` Mark Brown
2025-05-28 13:01 ` Brett Mastbergen
2025-05-28 15:16 ` Markus Reichelt
2025-05-29 16:29 ` Hardik Garg [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=1748536185-5619-1-git-send-email-hargar@linux.microsoft.com \
--to=hargar@linux.microsoft.com \
--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@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;
as well as URLs for NNTP newsgroup(s).