qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rorie Reyes <rreyes@linux.ibm.com>
To: "Cédric Le Goater" <clg@redhat.com>,
	"Anthony Krowiak" <akrowiak@linux.ibm.com>,
	qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: pbonzini@redhat.com, cohuck@redhat.com, pasic@linux.ibm.com,
	jjherne@linux.ibm.com, borntraeger@linux.ibm.com,
	alex.williamson@redhat.com, thuth@redhat.com
Subject: Re: [RFC PATCH v9 4/4] s390: implementing CHSC SEI for AP config change
Date: Tue, 20 May 2025 06:17:17 -0700	[thread overview]
Message-ID: <95f61ae5-089f-41bb-aa34-e5db1af31214@linux.ibm.com> (raw)
In-Reply-To: <779b2cc9-a028-4b59-b72d-e361647996ea@redhat.com>

>>> diff --git a/hw/s390x/ap-stub.c b/hw/s390x/ap-stub.c
>>> new file mode 100644
>>> index 0000000000..e2dacff959
>>> --- /dev/null
>>> +++ b/hw/s390x/ap-stub.c
>>> @@ -0,0 +1,25 @@
>>> +/*
>>> + * VFIO based AP matrix device assignment
>>> + *
>>> + * Copyright 2025 IBM Corp.
>>> + * Author(s): Rorie Reyes <rreyes@linux.ibm.com>
>>> + *
>>> + * SPDX-License-Identifier: GPL-2.0-or-later
>>> + *
>>> + * This work is licensed under the terms of the GNU GPL, version 2 
>>> or (at
>>> + * your option) any later version. See the COPYING file in the 
>>> top-level
>>> + * directory.
>
> FYI, I dropped the redundent license boilerplate. See [1].
>
> C.
>
> [1] 
> https://github.com/legoater/qemu/commit/8db3dbac401c56da6e865dcba1304f305555c22d
>
No problem! Thank you Cedric


  reply	other threads:[~2025-05-20 13:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12 18:02 [RFC PATCH v9 0/4] Report vfio-ap configuration changes Rorie Reyes
2025-05-12 18:02 ` [RFC PATCH v9 1/4] hw/vfio/ap: notification handler for AP config changed event Rorie Reyes
2025-05-12 18:02 ` [RFC PATCH v9 2/4] hw/vfio/ap: store object indicating AP config changed in a queue Rorie Reyes
2025-05-13 11:38   ` Anthony Krowiak
2025-05-22 13:27   ` Cédric Le Goater
2025-05-22 14:28     ` Rorie Reyes
2025-05-22 15:36       ` Cédric Le Goater
2025-05-22 15:55         ` Rorie Reyes
2025-05-23  2:30         ` Rorie Reyes
2025-05-12 18:02 ` [RFC PATCH v9 3/4] hw/vfio/ap: Storing event information for an AP configuration change event Rorie Reyes
2025-05-13 11:38   ` Anthony Krowiak
2025-05-22 13:30   ` Cédric Le Goater
2025-05-22 17:17     ` Rorie Reyes
2025-05-22 19:05       ` Anthony Krowiak
2025-05-22 18:55     ` Anthony Krowiak
2025-05-26  8:43       ` Cédric Le Goater
2025-05-27 11:58         ` Anthony Krowiak
2025-05-22 13:35   ` Cédric Le Goater
2025-05-22 19:02     ` Anthony Krowiak
2025-05-23  3:05       ` Rorie Reyes
2025-05-23  3:27         ` Rorie Reyes
2025-05-12 18:02 ` [RFC PATCH v9 4/4] s390: implementing CHSC SEI for AP config change Rorie Reyes
2025-05-13 11:08   ` Cédric Le Goater
2025-05-13 11:38   ` Anthony Krowiak
2025-05-20  6:52     ` Cédric Le Goater
2025-05-20 13:17       ` Rorie Reyes [this message]
2025-05-13 11:47 ` [RFC PATCH v9 0/4] Report vfio-ap configuration changes Cédric Le Goater

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=95f61ae5-089f-41bb-aa34-e5db1af31214@linux.ibm.com \
    --to=rreyes@linux.ibm.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=clg@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=jjherne@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.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;
as well as URLs for NNTP newsgroup(s).