From: Pierre Morel <pmorel@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, david@redhat.com, thuth@redhat.com,
cohuck@redhat.com, drjones@redhat.com
Subject: Re: [kvm-unit-tests PATCH v13 6/9] s390x: Library resources for CSS tests
Date: Thu, 16 Jul 2020 13:27:36 +0200 [thread overview]
Message-ID: <196f3522-1880-c178-6ddd-56dd2d0b5256@linux.ibm.com> (raw)
In-Reply-To: <9d6f0445-9c13-c23b-6095-0699ad09be87@linux.ibm.com>
On 2020-07-16 13:15, Janosch Frank wrote:
> On 7/16/20 10:23 AM, Pierre Morel wrote:
>> Provide some definitions and library routines that can be used by
>> tests targeting the channel subsystem.
>>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> Acked-by: Thomas Huth <thuth@redhat.com>
>> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
>> Acked-by: Janosch Frank <frankja@de.ibm.com>
>> ---
> [...]
>> diff --git a/s390x/Makefile b/s390x/Makefile
>> index ddb4b48..050c40b 100644
>> --- a/s390x/Makefile
>> +++ b/s390x/Makefile
>> @@ -51,6 +51,7 @@ cflatobjs += lib/s390x/sclp-console.o
>> cflatobjs += lib/s390x/interrupt.o
>> cflatobjs += lib/s390x/mmu.o
>> cflatobjs += lib/s390x/smp.o
>> +cflatobjs += lib/s390x/css_dump.o
>>
>> OBJDIRS += lib/s390x
>>
>
> I need to fix this up when picking because Thomas added vm.o after smp.o.
> Can I do that or do you want to rebase on my next branch?
>
>
I can do it and respin, that will give me the occasion to suppress the
goto as demanded by Thomas.
Is it OK?
--
Pierre Morel
IBM Lab Boeblingen
next prev parent reply other threads:[~2020-07-16 11:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 8:23 [kvm-unit-tests PATCH v13 0/9] s390x: Testing the Channel Subsystem I/O Pierre Morel
2020-07-16 8:23 ` [kvm-unit-tests PATCH v13 1/9] s390x: saving regs for interrupts Pierre Morel
2020-07-16 8:23 ` [kvm-unit-tests PATCH v13 2/9] s390x: I/O interrupt registration Pierre Morel
2020-07-16 8:23 ` [kvm-unit-tests PATCH v13 3/9] s390x: export the clock get_clock_ms() utility Pierre Morel
2020-07-16 8:23 ` [kvm-unit-tests PATCH v13 4/9] s390x: clock and delays calculations Pierre Morel
2020-07-16 8:23 ` [kvm-unit-tests PATCH v13 5/9] s390x: define function to wait for interrupt Pierre Morel
2020-07-16 8:23 ` [kvm-unit-tests PATCH v13 6/9] s390x: Library resources for CSS tests Pierre Morel
2020-07-16 11:15 ` Janosch Frank
2020-07-16 11:27 ` Pierre Morel [this message]
2020-07-16 11:31 ` Janosch Frank
2020-07-16 13:02 ` [PATCH v14 " Pierre Morel
2020-07-16 13:02 ` [PATCH v14 7/9] s390x: css: stsch, enumeration test Pierre Morel
2020-07-16 8:23 ` [kvm-unit-tests PATCH v13 " Pierre Morel
2020-07-16 8:23 ` [kvm-unit-tests PATCH v13 8/9] s390x: css: msch, enable test Pierre Morel
2020-07-16 8:23 ` [kvm-unit-tests PATCH v13 9/9] s390x: css: ssch/tsch with sense and interrupt Pierre Morel
2020-07-16 8:46 ` Thomas Huth
2020-07-16 8:58 ` Pierre Morel
2020-07-16 13:04 ` [PATCH v14 " Pierre Morel
2020-07-16 9:07 ` [kvm-unit-tests PATCH v13 " Cornelia Huck
2020-07-21 13:11 ` [kvm-unit-tests PATCH v13 0/9] s390x: Testing the Channel Subsystem I/O Janosch Frank
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=196f3522-1880-c178-6ddd-56dd2d0b5256@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=drjones@redhat.com \
--cc=frankja@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