public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Collin Walling <walling@linux.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org
Cc: pbonzini@redhat.com, frankja@linux.ibm.com, david@redhat.com,
	cohuck@redhat.com, imbrenda@linux.ibm.com,
	heiko.carstens@de.ibm.com, gor@linux.ibm.com, thuth@redhat.com
Subject: Re: [PATCH v9 0/2] Use DIAG318 to set Control Program Name & Version Codes
Date: Tue, 23 Jun 2020 10:38:13 -0400	[thread overview]
Message-ID: <704fd712-1883-9aad-bb60-4412cb8a9573@linux.ibm.com> (raw)
In-Reply-To: <cfe77de0-e1d8-5779-541f-286cf3002459@de.ibm.com>

On 6/23/20 3:13 AM, Christian Borntraeger wrote:
> 
> 
> On 22.06.20 17:46, Collin Walling wrote:
>> Changelog:
>>
>>     v9
>>
>>     • No longer unshadowing CPNC in VSIE
>>
> applied. 
> 

Thanks!

-- 
Regards,
Collin

Stay safe and stay healthy

      reply	other threads:[~2020-06-23 14:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 15:46 [PATCH v9 0/2] Use DIAG318 to set Control Program Name & Version Codes Collin Walling
2020-06-22 15:46 ` [PATCH v9 1/2] s390/setup: diag 318: refactor struct Collin Walling
2020-06-22 15:46 ` [PATCH v9 2/2] s390/kvm: diagnose 0x318 sync and reset Collin Walling
2020-06-22 16:04   ` Cornelia Huck
2020-06-22 16:13     ` Collin Walling
2020-06-22 16:23       ` Collin Walling
2020-06-22 16:35         ` Cornelia Huck
2020-06-22 16:45           ` Collin Walling
2020-06-23  7:12   ` David Hildenbrand
2020-06-23  8:42   ` Thomas Huth
2020-06-23  8:45     ` Christian Borntraeger
2020-06-23  8:47       ` Christian Borntraeger
2020-06-23  8:58         ` Thomas Huth
2020-06-23  7:13 ` [PATCH v9 0/2] Use DIAG318 to set Control Program Name & Version Codes Christian Borntraeger
2020-06-23 14:38   ` Collin Walling [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=704fd712-1883-9aad-bb60-4412cb8a9573@linux.ibm.com \
    --to=walling@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --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