From: Hardik Garg <hargar@linux.microsoft.com>
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,
Hardik Garg <hargar@linux.microsoft.com>
Subject: Re: [PATCH 6.18 000/175] 6.18.10-rc1 review
Date: Mon, 9 Feb 2026 12:54:32 -0800 [thread overview]
Message-ID: <20260209205432.1216109-1-hargar@linux.microsoft.com> (raw)
In-Reply-To: <20260209142320.474120190@linuxfoundation.org>
The kernel, bpf tool, perf tool, and kselftest builds fine for
v6.18.10-rc1 on x86 and arm64 Azure VM.
Tested-by: Hardik Garg <hargar@linux.microsoft.com>
Thanks,
Hardik
next prev parent reply other threads:[~2026-02-09 20:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 14:21 [PATCH 6.18 000/175] 6.18.10-rc1 review Greg Kroah-Hartman
2026-02-09 17:24 ` Ronald Warsow
2026-02-09 18:23 ` Luna Jernberg
2026-02-09 18:16 ` Brett A C Sheffield
2026-02-09 20:24 ` Peter Schneider
2026-02-09 20:54 ` Hardik Garg [this message]
2026-02-09 20:55 ` Jon Hunter
2026-02-09 23:32 ` Takeshi Ogasawara
2026-02-10 3:07 ` Justin Forbes
2026-02-10 7:46 ` Ron Economos
2026-02-10 12:59 ` Mark Brown
2026-02-10 15:04 ` Jeffrin Thalakkottoor
2026-02-10 15:43 ` Greg Kroah-Hartman
2026-02-10 16:42 ` Jeffrin Thalakkottoor
2026-02-10 17:21 ` Florian Fainelli
2026-02-10 20:05 ` Dileep malepu
2026-02-11 4:25 ` Shung-Hsi Yu
2026-02-11 10:33 ` Barry K. Nathan
2026-02-11 13:45 ` Miguel Ojeda
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=20260209205432.1216109-1-hargar@linux.microsoft.com \
--to=hargar@linux.microsoft.com \
--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