From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] f2fs-tools: add big-endian fixes/patches from upstream
Date: Tue, 23 Dec 2014 20:56:04 +0100 [thread overview]
Message-ID: <20141223205604.01741f97@free-electrons.com> (raw)
In-Reply-To: <1419352039-9384-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Tue, 23 Dec 2014 13:27:19 -0300, Gustavo Zacarias wrote:
> Fixes:
> http://autobuild.buildroot.net/results/8f9/8f97186489134619de7086028a59523d528b0d51/
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> ...tools-fix-for-build-big-endian-processors.patch | 95 ++++++++++++++++++++++
> ...sible-endianes-bug-in-mkfs.f2fs-roll-forw.patch | 81 ++++++++++++++++++
> 2 files changed, 176 insertions(+)
> create mode 100644 package/f2fs-tools/0001-f2fs-tools-fix-for-build-big-endian-processors.patch
> create mode 100644 package/f2fs-tools/0002-mkfs.f2fs-possible-endianes-bug-in-mkfs.f2fs-roll-forw.patch
Applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-12-23 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 16:27 [Buildroot] [PATCH] f2fs-tools: add big-endian fixes/patches from upstream Gustavo Zacarias
2014-12-23 19:56 ` Thomas Petazzoni [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=20141223205604.01741f97@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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