From: Philip Balister <philip@balister.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>,
akuster808@gmail.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6][dizzy] some wic bugfixes
Date: Wed, 03 Dec 2014 08:40:18 -0500 [thread overview]
Message-ID: <547F12C2.5070700@balister.org> (raw)
In-Reply-To: <cover.1416585198.git.tom.zanussi@linux.intel.com>
On 11/21/2014 11:07 AM, Tom Zanussi wrote:
>>From the original posting:
>
> This patchset fixes a couple serious wic bugs:
>
> [YOCTO #6863] - Wic fails to create a working image for a large file system
> [YOCTO #6290] - Update WIC for gummiboot
>
> I generated core-image-sdk images for each of the wic image types and
> was able to fsck/mount the resulting filesystems.
>
> These should be applied to the next dizzy point release.
>
> The following changes since commit e69653b01dd8ad9fda2355b8112a65c813ce7fd5:
>
> tzdata: update to 2014j (2014-11-17 08:01:21 -0800)
>
> are available in the git repository at:
>
> git://git.yoctoproject.org/poky-contrib.git tzanussi/dizzy-next
> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=tzanussi/dizzy-next
>
> Tom Zanussi (6):
> wic: Don't allow mkfs to fail silently in partition command
> wic: Use overhead factor when creating partitions from rootfs
> directories
It looks like all the patches in this request made it into dizzy, except
the overhead factor one. Is there a reason for this? Can we get the
overhead one into dizzy also?
Philip
> wic: Update the help text to include -D (--debug)
> Revert "wic: set bootimg_dir when using image-name artifacts"
> wic: Remove special-case bootimg_dir
> wic: Update bootimg-partition to use bootimg_dir
>
> scripts/lib/image/engine.py | 42 +++++-----------------
> scripts/lib/image/help.py | 23 ++++++++----
> scripts/lib/wic/imager/direct.py | 5 +--
> .../lib/wic/kickstart/custom_commands/partition.py | 24 +++++++++----
> scripts/lib/wic/plugins/imager/direct_plugin.py | 20 +++++------
> scripts/lib/wic/plugins/source/bootimg-efi.py | 5 ++-
> .../lib/wic/plugins/source/bootimg-partition.py | 9 +++--
> scripts/lib/wic/plugins/source/bootimg-pcbios.py | 3 +-
> scripts/lib/wic/utils/oe/misc.py | 1 +
> scripts/wic | 13 +++----
> 10 files changed, 68 insertions(+), 77 deletions(-)
>
next prev parent reply other threads:[~2014-12-03 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 16:07 [PATCH 0/6][dizzy] some wic bugfixes Tom Zanussi
2014-11-21 16:07 ` [PATCH 1/6][dizzy] wic: Don't allow mkfs to fail silently in partition command Tom Zanussi
2014-11-21 16:07 ` [PATCH 2/6][dizzy] wic: Use overhead factor when creating partitions from rootfs directories Tom Zanussi
2014-11-21 16:07 ` [PATCH 3/6][dizzy] wic: Update the help text to include -D (--debug) Tom Zanussi
2014-11-21 16:07 ` [PATCH 4/6][dizzy] Revert "wic: set bootimg_dir when using image-name artifacts" Tom Zanussi
2014-11-21 16:07 ` [PATCH 5/6][dizzy] wic: Remove special-case bootimg_dir Tom Zanussi
2014-11-21 16:07 ` [PATCH 6/6][dizzy] wic: Update bootimg-partition to use bootimg_dir Tom Zanussi
2014-11-21 21:48 ` [PATCH 0/6][dizzy] some wic bugfixes akuster808
2014-12-03 13:40 ` Philip Balister [this message]
2014-12-03 15:50 ` akuster808
2014-12-03 17:58 ` Tom Zanussi
2014-12-03 16:28 ` akuster808
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=547F12C2.5070700@balister.org \
--to=philip@balister.org \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tom.zanussi@linux.intel.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