All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Ed Bartosh <ed.bartosh@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] wic: When using --use-uuid make sure that we update the fstab with PARTUUID
Date: Tue, 7 Nov 2017 09:55:53 -0500	[thread overview]
Message-ID: <20171107145553.GK32663@bill-the-cat> (raw)
In-Reply-To: <20171107082725.lzsbsnqrypbm525v@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

On Tue, Nov 07, 2017 at 10:27:25AM +0200, Ed Bartosh wrote:
> On Mon, Nov 06, 2017 at 07:44:17AM -0500, Tom Rini wrote:
> > > Can you rebase your patchset on top of current master?
> > 
> > Yes, OK.
> > 
> > > It would be also nice to get this functionality covered by tests.
> > 
> > OK, but what part of oe-selftest, and how exactly?  Can one easily check
> > the resulting fstab?
> 
> Sorry for not mentioning it. You can look at wic oe-selftest test cases
> in meta/lib/oeqa/selftest/cases/wic.py
> 
> To check image fstab you can boot image in qemu (see test cases
> starting with 'test_qemu' for the reference). This way you can also
> check if partition uids match fstab entries.
> 
> P.S. Another idea is to extending 'wic cp' or implement 'wic cat'. All
> ingredients are already in the wic code, so it shouldn't be too hard.

OK, I'll see what I can figure out here, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2017-11-07 14:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 17:46 [PATCH 1/2] wic: When using --use-uuid make sure that we update the fstab with PARTUUID Tom Rini
2017-09-21 17:46 ` [PATCH 2/2] wic: Update canned-wks for systemd to use UUID everywhere Tom Rini
2017-09-21 21:15 ` [PATCH 1/2] wic: When using --use-uuid make sure that we update the fstab with PARTUUID Otavio Salvador
2017-09-21 21:19   ` Tom Rini
2017-09-21 21:20   ` Mark Hatle
2017-09-21 21:21     ` Tom Rini
2017-09-28 12:26       ` Ed Bartosh
2017-10-10 21:01 ` Tom Rini
2017-10-20 13:15   ` Tom Rini
2017-11-03 12:51     ` Tom Rini
2017-11-06 10:08       ` Ed Bartosh
2017-11-06 11:36         ` Otavio Salvador
2017-11-06 12:44           ` Tom Rini
2017-11-06 12:51             ` Otavio Salvador
2017-11-06 13:02               ` Tom Rini
2017-11-07  8:11             ` Ed Bartosh
2017-11-07 14:54               ` Tom Rini
2017-11-08 11:20                 ` Ed Bartosh
2017-11-08 15:00                   ` Tom Rini
2017-11-08 14:30                     ` Ed Bartosh
2017-11-06 12:44         ` Tom Rini
2017-11-07  8:27           ` Ed Bartosh
2017-11-07 14:55             ` Tom Rini [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=20171107145553.GK32663@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=ed.bartosh@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.