public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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@denx.de,
	rwarsow@gmx.de, shuah@kernel.org, stable@vger.kernel.org,
	sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 6.6 000/201] 6.6.113-rc1 review
Date: Fri, 17 Oct 2025 14:44:50 -0700	[thread overview]
Message-ID: <1760737490-28442-1-git-send-email-hargar@linux.microsoft.com> (raw)
In-Reply-To: <20251017145134.710337454@linuxfoundation.org>

The kernel, bpf tool, perf tool, and kselftest builds fine for v6.6.113-rc1 on x86 and arm64 Azure VM.


Tested-by: Hardik Garg <hargar@linux.microsoft.com>


Thanks,
Hardik

  parent reply	other threads:[~2025-10-17 21:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17 14:51 [PATCH 6.6 000/201] 6.6.113-rc1 review Greg Kroah-Hartman
2025-10-17 14:51 ` [PATCH 6.6 039/201] tools build: Align warning options with perf Greg Kroah-Hartman
2025-10-17 14:51 ` [PATCH 6.6 040/201] perf python: split Clang options when invoking Popen Greg Kroah-Hartman
2025-10-17 18:21 ` [PATCH 6.6 000/201] 6.6.113-rc1 review Jon Hunter
2025-10-17 21:44 ` Hardik Garg [this message]
2025-10-18  0:25 ` Shuah Khan
2025-10-18  2:43 ` Peter Schneider
2025-10-18  3:16 ` Florian Fainelli
2025-10-18  8:14 ` Brett A C Sheffield
2025-10-18 10:42 ` Naresh Kamboju
2025-10-18 16:09 ` 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=1760737490-28442-1-git-send-email-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@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --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