From: Janosch Frank <frankja@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH 0/3] s390x: More emulation tests
Date: Wed, 21 Aug 2019 11:28:45 +0200 [thread overview]
Message-ID: <6c6fb63c-af8a-ecea-957b-9e5a48edf399@linux.ibm.com> (raw)
In-Reply-To: <6addbd2b-435b-9367-8a13-152b094707ac@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1837 bytes --]
On 8/21/19 10:53 AM, David Hildenbrand wrote:
> On 21.08.19 10:48, Janosch Frank wrote:
>> On 8/20/19 9:04 PM, David Hildenbrand wrote:
>>> On 20.08.19 12:55, Janosch Frank wrote:
>>>> The first patch allows for CECSIM booting via PSW restart.
>>>> The other ones add diag288 and STSI tests.
>>>>
>>>> I chose to start with these since they are low controversy. My queue
>>>> still contains the sclp patches and a simple smp library with
>>>> tests. They will follow later.
>>>
>>> On which branch do these patches apply? I fail to am 2+3 on master (well
>>> I didn't try too hard to resolve ;) ). Do you have a branch somewhere?
>>>
>>
>> That is currently on top of master (24efc22), the only merge conflicts
>> might be s390x/Makefile or unittests.conf if your branch is not clean.
>> I'm trying to get a public github account for that and qemu.
>>
>
> t460s: ~/git/kvm-unit-tests master $ git fetch origin
> t460s: ~/git/kvm-unit-tests master $ git reset --hard origin/master
> HEAD is now at 03b1e45 x86: Support environments without test-devices
> t460s: ~/git/kvm-unit-tests master $ git am \[kvm-unit-tests\ PATCH\ *
> Applying: s390x: Support PSW restart boot
> Applying: s390x: Diag288 test
> error: patch failed: s390x/Makefile:11
> error: s390x/Makefile: patch does not apply
> error: patch failed: s390x/unittests.cfg:61
> error: s390x/unittests.cfg: patch does not apply
> Patch failed at 0002 s390x: Diag288 test
> hint: Use 'git am --show-current-patch' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
> Are you sure?
>
The internal mirror did not pick up the changes of the last few days...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-08-21 9:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 10:55 [kvm-unit-tests PATCH 0/3] s390x: More emulation tests Janosch Frank
2019-08-20 10:55 ` [kvm-unit-tests PATCH 1/3] s390x: Support PSW restart boot Janosch Frank
2019-08-20 11:40 ` Thomas Huth
2019-08-20 10:55 ` [kvm-unit-tests PATCH 2/3] s390x: Diag288 test Janosch Frank
2019-08-20 11:59 ` Thomas Huth
2019-08-20 12:25 ` Janosch Frank
2019-08-20 12:55 ` Thomas Huth
2019-08-20 15:21 ` Janosch Frank
2019-08-20 15:29 ` Thomas Huth
2019-08-20 10:55 ` [kvm-unit-tests PATCH 3/3] s390x: STSI tests Janosch Frank
2019-08-20 13:21 ` Thomas Huth
2019-08-21 8:46 ` Janosch Frank
2019-08-20 11:11 ` [kvm-unit-tests PATCH 0/3] s390x: More emulation tests David Hildenbrand
2019-08-20 11:49 ` Janosch Frank
2019-08-20 19:04 ` David Hildenbrand
2019-08-21 8:48 ` Janosch Frank
2019-08-21 8:53 ` David Hildenbrand
2019-08-21 9:28 ` Janosch Frank [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=6c6fb63c-af8a-ecea-957b-9e5a48edf399@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=david@redhat.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