From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: dvhart@linux.intel.com
Subject: Re: [PATCH 0/1] mkdosfs populated image creation fix version:2
Date: Thu, 15 Dec 2011 11:28:15 -0800 [thread overview]
Message-ID: <4EEA4A4F.4090102@linux.intel.com> (raw)
In-Reply-To: <cover.1323913192.git.nitin.a.kamble@intel.com>
On 12/14/2011 05:47 PM, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble<nitin.a.kamble@intel.com>
>
> This has enhanced the commit for fixing mkdosfs. We noticed some
> issues with the generated image with the earlier sent-out commit.
> This version 2 commit has improved the the mkdosfs further. Now
> the outstanding issues in the image are fixable by dosfsck.
> More details are in the patch documentation.
>
> Thanks,
> Nitin
>
> The following changes since commit 9d136b2db8f906c562cbdb23a9b238f0e237074b:
>
> gdk-pixbuf: Ensure the binaries can be relocated (2011-12-13 18:00:25 +0000)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib nitin/bugfix
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/bugfix
>
> Nitin A Kamble (1):
> dosfstools: fix populated image creation with dirs
>
> .../dosfstools/fix_populated_dosfs_creation.patch | 489 ++++++++++++++++++++
> .../recipes-devtools/dosfstools/dosfstools_2.11.bb | 5 +-
> 2 files changed, 492 insertions(+), 2 deletions(-)
> create mode 100644 meta/recipes-devtools/dosfstools/dosfstools/fix_populated_dosfs_creation.patch
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2011-12-15 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 1:47 [PATCH 0/1] mkdosfs populated image creation fix version:2 nitin.a.kamble
2011-12-15 1:47 ` [PATCH 1/1] dosfstools: fix populated image creation with dirs nitin.a.kamble
2011-12-15 20:42 ` Darren Hart
2011-12-15 22:03 ` Kamble, Nitin A
2011-12-16 0:15 ` Darren Hart
2011-12-15 19:28 ` Saul Wold [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=4EEA4A4F.4090102@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=dvhart@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox