From: Jan Kiszka <jan.kiszka@siemens.com>
To: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>,
<isar-users@googlegroups.com>
Cc: <henning.schild@siemens.com>
Subject: Re: [PATCH 1/2] meta-isar/wks: prepare wks for wic uprev
Date: Mon, 13 Jun 2022 09:16:25 +0200 [thread overview]
Message-ID: <0a8903ab-ff17-594c-58c9-f4c4db73d831@siemens.com> (raw)
In-Reply-To: <20220610113919.2051302-2-Vijaikumar_Kanagarajan@mentor.com>
On 10.06.22 13:39, Vijai Kumar K wrote:
> In the current version of wic we use, "/" mount points are ignored and
> their entries are not added to fstab.
>
> But in the latest version of wic available in oe-core, this is not the case.
> "/" mountpoints are respected and are added to fstab.
>
> ISAR already creates the necessary fstab. With the new version we will
> end up with 2 entries for "/". One from ISAR's image_configure_fstab and
> the other one appended by wic.
>
> Explicitly drop "/" mountpoint args in wks files to avoid this.
>
Wrong patch ordering.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-06-13 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 11:39 [PATCH 0/2] Update wic to bring in fspassno feature Vijai Kumar K
2022-06-10 11:39 ` [PATCH 1/2] meta-isar/wks: prepare wks for wic uprev Vijai Kumar K
2022-06-13 7:16 ` Jan Kiszka [this message]
2022-06-13 7:36 ` Kanagarajan, Vijaikumar
2022-06-13 8:10 ` Henning Schild
2022-06-13 8:35 ` Kanagarajan, Vijaikumar
2022-06-13 9:26 ` Henning Schild
2022-06-10 11:39 ` [PATCH 2/2] wic: Update to the latest revision Vijai Kumar K
2022-06-13 7:15 ` [PATCH 0/2] Update wic to bring in fspassno feature Jan Kiszka
2022-06-13 7:21 ` Anton Mikanovich
2022-06-13 7:32 ` Kanagarajan, Vijaikumar
2022-06-13 8:31 ` Henning Schild
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=0a8903ab-ff17-594c-58c9-f4c4db73d831@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Vijaikumar_Kanagarajan@mentor.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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