Thomas Huth writes:
> Since we can now use a s390x host on Travis, we can also build and
> test the s390-ccw bios images there. For this we have to make sure
> that roms/SLOF is checked out, too, and then move the generated *.img
> files to the right location before running the tests.
>
>
On 07.02.20 10:56, Thomas Huth wrote:
> On 07/02/2020 10.47, Cornelia Huck wrote:
>> On Thu, 6 Feb 2020 21:25:43 +0100
>> Thomas Huth wrote:
>>
>>> Since we can now use a s390x host on Travis, we can also build and
>>> test the s390-ccw bios images there. For this we have to make sure
>>>
On 07/02/2020 10.47, Cornelia Huck wrote:
> On Thu, 6 Feb 2020 21:25:43 +0100
> Thomas Huth wrote:
>
>> Since we can now use a s390x host on Travis, we can also build and
>> test the s390-ccw bios images there. For this we have to make sure
>> that roms/SLOF is checked out, too, and then move
On Thu, 6 Feb 2020 21:25:43 +0100
Thomas Huth wrote:
> Since we can now use a s390x host on Travis, we can also build and
> test the s390-ccw bios images there. For this we have to make sure
> that roms/SLOF is checked out, too, and then move the generated *.img
> files to the right location
On 2/6/20 9:25 PM, Thomas Huth wrote:
Since we can now use a s390x host on Travis, we can also build and
test the s390-ccw bios images there. For this we have to make sure
that roms/SLOF is checked out, too, and then move the generated *.img
files to the right location before running the tests.
Since we can now use a s390x host on Travis, we can also build and
test the s390-ccw bios images there. For this we have to make sure
that roms/SLOF is checked out, too, and then move the generated *.img
files to the right location before running the tests.
Signed-off-by: Thomas Huth
---