public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>,
	isar-users <isar-users@googlegroups.com>
Cc: Henning Schild <henning.schild@siemens.com>,
	Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: Re: [PATCH] wic-img: Fix bind mounting
Date: Fri, 7 Dec 2018 12:33:59 +0100	[thread overview]
Message-ID: <0175c45c-f8ee-3875-7638-01d421aa0dcc@siemens.com> (raw)
In-Reply-To: <2c2a8362-185d-5009-c1ad-716b3cd88749@ilbers.de>

Hi Maxim,

On 07.12.18 12:18, Maxim Yu. Osipov wrote:
> Hi Jan,
> 
> On 12/6/18 2:17 PM, Jan Kiszka wrote:
>> On 06.12.18 10:44, Maxim Yu. Osipov wrote:
>>> Just to doublecheck: What is your patch queue for that?
>>>
>>
>> Just updated jan/queue on github.com/siemens/isar. It's not the best ordering 
>> of patches, this fix should probably come earlier, but the top is what I 
>> tested successfully also in a stretch VM.
> 
> I'm convinced that this patch fixes these two issues.
> CI passes OK on my stretch laptop.
> It fails on isar-build.org by evident reason (CI runs in stretch chroot on 
> jessie host - the host's kernel 3.16 has troubles with 'mount --rbind'). We are 
> now upgrading the host system.

Should we document this dependency "host >= stretch" somewhere, or did we already?

> 
> When applying to the 'next' I may rearrange the ordering of patches in more 
> logical path
> 
> git log --oneline:
> 
> c46ad1b isar-image: Make do_rootfs normal shell function
> 05d0fc4 isar-events: Improve umount handler
> 93c4795 ci: Make partial rebuild test non-destructive
> 4ca0bff ci: Wait for bitbake worker to finish before deleting artifacts
> 698fb56 Remove redundant recursive umounts
> bbc61fb wic-img: Fix bind mounting
> 9cf29e6 isar-bootstrap: Fix and cleanup bind mounting
> b354026 isar-image: umount base-apt when doing offline build
> e965c0d gitlab-ci: Switch to ci_build.sh
> 
> is it OK?
> 

Looks good to me.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-12-07 11:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06  8:13 Jan Kiszka
2018-12-06  9:44 ` Maxim Yu. Osipov
2018-12-06 11:17   ` Jan Kiszka
2018-12-07 11:18     ` Maxim Yu. Osipov
2018-12-07 11:33       ` Jan Kiszka [this message]
2018-12-07 13:48 ` 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=0175c45c-f8ee-3875-7638-01d421aa0dcc@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Cedric_Hombourger@mentor.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=mosipov@ilbers.de \
    /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