mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	pbonzini@redhat.com,  Hisam Mehboob <hisamshar@gmail.com>
Cc: maz@kernel.org, oupton@kernel.org, joey.gouly@arm.com,
	 seiden@linux.ibm.com, suzuki.poulose@arm.com,
	yuzenghui@huawei.com,  shuah@kernel.org, aqibaf@amazon.com,
	linux-arm-kernel@lists.infradead.org,  kvmarm@lists.linux.dev,
	kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
	 linux-kernel@vger.kernel.org, Fuad Tabba <fuad.tabba@linux.dev>
Subject: Re: [PATCH v2] KVM: selftests: Replace ulong with unsigned long
Date: Mon, 21 Sep 2026 07:05:34 -0700	[thread overview]
Message-ID: <178999928264.755166.909574492736686331.b4-ty@google.com> (raw)
In-Reply-To: <20260803170825.925561-4-hisamshar@gmail.com>

On Mon, 03 Aug 2026 22:08:28 +0500, Hisam Mehboob wrote:
> KVM selftests use the non-standard ulong alias in several files. glibc
> exposes the alias transitively through its headers, whereas musl does not,
> causing musl builds to fail with ulong undeclared.
> 
> Use unsigned long directly instead of depending on a libc-specific typedef.
> This also avoids adding a duplicate typedef to a shared tools header.
> 
> [...]

Applied to kvm-x86 selftests, thanks!

[1/1] KVM: selftests: Replace ulong with unsigned long
      https://github.com/kvm-x86/linux/commit/5be2d20f9818

--
https://github.com/kvm-x86/linux/tree/next

      reply	other threads:[~2026-09-21 14:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 17:08 Hisam Mehboob
2026-09-21 14:05 ` Sean Christopherson [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=178999928264.755166.909574492736686331.b4-ty@google.com \
    --to=seanjc@google.com \
    --cc=aqibaf@amazon.com \
    --cc=fuad.tabba@linux.dev \
    --cc=hisamshar@gmail.com \
    --cc=joey.gouly@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=oupton@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seiden@linux.ibm.com \
    --cc=shuah@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=yuzenghui@huawei.com \
    /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

all inboxes | Powered by JetHome®