All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hardik Garg <hargar@linux.microsoft.com>
To: sashal@kernel.org
Cc: achill@achill.org, akpm@linux-foundation.org, broonie@kernel.org,
	conor@kernel.org, f.fainelli@gmail.com,
	gregkh@linuxfoundation.org, 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.19 000/850] 6.19.6-rc2 review
Date: Tue,  3 Mar 2026 22:21:15 -0800	[thread overview]
Message-ID: <20260304062115.350642-1-hargar@linux.microsoft.com> (raw)
In-Reply-To: <20260302160834.2518716-1-sashal@kernel.org>

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


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


Thanks,
Hardik

  parent reply	other threads:[~2026-03-04  6:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 16:08 [PATCH 6.19 000/850] 6.19.6-rc2 review Sasha Levin
2026-03-02 19:35 ` Brett A C Sheffield
2026-03-02 22:15 ` Justin Forbes
2026-03-03  2:03 ` Peter Schneider
2026-03-03  5:36 ` Florian Fainelli
2026-03-03  7:21 ` Takeshi Ogasawara
2026-03-03  8:19 ` Shung-Hsi Yu
2026-03-03  8:23 ` Barry K. Nathan
2026-03-03 11:57 ` Ron Economos
2026-03-03 14:12 ` Jon Hunter
2026-03-03 18:19 ` Mark Brown
2026-03-03 21:44 ` Miguel Ojeda
2026-03-04  6:21 ` Hardik Garg [this message]
2026-03-04 17:47 ` Shuah Khan

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=20260304062115.350642-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=sashal@kernel.org \
    --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 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.