Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Hisam Mehboob <hisamshar@gmail.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, seanjc@google.com, shuah@kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2] KVM: selftests: Replace ulong with unsigned long
Date: Tue, 18 Aug 2026 03:04:59 +0500	[thread overview]
Message-ID: <20260817220457.554823-3-hisamshar@gmail.com> (raw)
In-Reply-To: <20260803170825.925561-4-hisamshar@gmail.com>

Gentle ping on this patch; it has been on the list since Aug 3 without
any comments.

The musl build failure it fixes is still present in current trees, and
the v1 feedback was addressed in this version. Could it be queued in
kvm-next?

Thanks,
Hisam

  reply	other threads:[~2026-08-17 22:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 17:08 [PATCH v2] KVM: selftests: Replace ulong with unsigned long Hisam Mehboob
2026-08-17 22:04 ` Hisam Mehboob [this message]
2026-08-17 22:24   ` Sean Christopherson
2026-08-17 22:42     ` Hisam Mehboob
2026-08-18 16:27       ` Sean Christopherson
2026-08-18 18:19         ` Hisam Mehboob
2026-08-18 19:28           ` Sean Christopherson

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=20260817220457.554823-3-hisamshar@gmail.com \
    --to=hisamshar@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=shuah@kernel.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