Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: ARMLinux <linux-arm-kernel@lists.infradead.org>,
	KVMARM <kvmarm@lists.linux.dev>,
	Jing Zhang <jingzhangos@google.com>,
	Marc Zyngier <maz@kernel.org>, KVM <kvm@vger.kernel.org>
Cc: Oliver Upton <oliver.upton@linux.dev>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Itaru Kitayama <itaru.kitayama@fujitsu.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Itaru Kitayama <itaru.kitayama@linux.dev>,
	Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH v2] KVM: arm64: selftests: Handle feature fields with nonzero minimum value correctly
Date: Wed, 24 Jan 2024 20:59:48 +0000	[thread overview]
Message-ID: <170612997432.109327.7730932953409830369.b4-ty@linux.dev> (raw)
In-Reply-To: <20240115220210.3966064-2-jingzhangos@google.com>

On Mon, 15 Jan 2024 14:02:09 -0800, Jing Zhang wrote:
> There are some feature fields with nonzero minimum valid value. Make
> sure get_safe_value() won't return invalid field values for them.
> Also fix a bug that wrongly uses the feature bits type as the feature
> bits sign causing all fields as signed in the get_safe_value() and
> get_invalid_value().
> 
> 
> [...]

Applied to kvmarm/next, thanks!

[1/1] KVM: arm64: selftests: Handle feature fields with nonzero minimum value correctly
      https://git.kernel.org/kvmarm/kvmarm/c/1cd2b08f7cc4

--
Best,
Oliver

      parent reply	other threads:[~2024-01-24 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 22:02 [PATCH v1] KVM: arm64: selftests: Handle feature fields with nonzero minimum value correctly Jing Zhang
2024-01-15 22:02 ` [PATCH v2] " Jing Zhang
2024-01-15 23:07   ` Itaru Kitayama
2024-01-24 20:59   ` Oliver Upton [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=170612997432.109327.7730932953409830369.b4-ty@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=itaru.kitayama@fujitsu.com \
    --cc=itaru.kitayama@linux.dev \
    --cc=james.morse@arm.com \
    --cc=jingzhangos@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maz@kernel.org \
    --cc=pbonzini@redhat.com \
    --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