From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] linux-custom: Add support for kernels >= 4.17
Date: Mon, 1 Oct 2018 12:02:14 +0300 [thread overview]
Message-ID: <5ce36f63-0e66-8af1-6490-7bb5dde46b01@ilbers.de> (raw)
In-Reply-To: <63219fcc-4ed0-fb55-ab48-f39f21eb524e@siemens.com>
On 10/1/18 11:50 AM, Jan Kiszka wrote:
> On 01.10.18 10:19, Jan Kiszka wrote:
>> On 01.10.18 09:54, Jan Kiszka wrote:
>>> On 01.10.18 09:46, Maxim Yu. Osipov wrote:
>>>> Hi Jan,
>>>>
>>>> Should we include your two last linux-custom patches into the
>>>> release (I planned to release isar today evening)?
>>>
>>> Yes, I think so. I've tested both with jailhouse-images for 4.14 and
>>> 4.19-rc, so I feel rather confident that they work as desired. I'll
>>> do a 4.4-cip check this morning as well and scream out loudly if that
>>> should break unexpectedly.
>>
>> 4.4-build completed successfully as well.
>
> BTW, do you have a kernel build as part of your CI? If not, should we
> add this? Ideally there would even be a build of latest linus-master to
> catch issues like these here.
This is in CI TODO list...
Maxim.
> Jan
>
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2018-10-01 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 16:55 Jan Kiszka
2018-10-01 7:46 ` Maxim Yu. Osipov
2018-10-01 7:54 ` Jan Kiszka
2018-10-01 8:19 ` Jan Kiszka
2018-10-01 8:50 ` Jan Kiszka
2018-10-01 9:02 ` Maxim Yu. Osipov [this message]
2018-10-01 10:51 ` Maxim Yu. Osipov
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=5ce36f63-0e66-8af1-6490-7bb5dde46b01@ilbers.de \
--to=mosipov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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