public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: David Hildenbrand <david@redhat.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v1] s390x: Fix integer literal in skey.c
Date: Wed, 04 Jan 2023 19:05:33 +0100	[thread overview]
Message-ID: <6d23c99ad1d799f72a171c02fa3bd20870ba6c7e.camel@linux.ibm.com> (raw)
In-Reply-To: <20230104175950.731988-1-nsg@linux.ibm.com>

I forgot:

Fixes: 965e38a0 ("s390x: Test effect of storage keys on diag 308")

On Wed, 2023-01-04 at 18:59 +0100, Nina Schoetterl-Glausch wrote:
> The code is a 64bit number of which the upper 48 bits must be 0.
> 
> Signed-off-by: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
> ---
>  s390x/skey.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/s390x/skey.c b/s390x/skey.c
> index 1167e4d3..7c7a8090 100644
> --- a/s390x/skey.c
> +++ b/s390x/skey.c
> @@ -320,7 +320,7 @@ static void test_diag_308(void)
>  		"lr	%[response],%%r3\n"
>  		: [response] "=d" (response)
>  		: [ipib] "d" (ipib),
> -		  [code] "d" (5)
> +		  [code] "d" (5L)
>  		: "%r2", "%r3"
>  	);
>  	report(response == 0x402, "no exception on fetch, response: invalid IPIB");
> 
> base-commit: 73d9d850f1c2c9f0df321967e67acda0d2c305ea


  reply	other threads:[~2023-01-04 18:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 17:59 [kvm-unit-tests PATCH v1] s390x: Fix integer literal in skey.c Nina Schoetterl-Glausch
2023-01-04 18:05 ` Nina Schoetterl-Glausch [this message]
2023-01-05 10:05 ` Thomas Huth

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=6d23c99ad1d799f72a171c02fa3bd20870ba6c7e.camel@linux.ibm.com \
    --to=nsg@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=thuth@redhat.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