From: Greg KH <gregkh@linuxfoundation.org>
To: Eunbong Song <eunb.song@samsung.com>
Cc: chanho.min@lge.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib : lz4 using put_unaligned_le16 instead of put_unaligned
Date: Mon, 21 Jul 2014 19:11:37 -0700 [thread overview]
Message-ID: <20140722021137.GD19215@kroah.com> (raw)
In-Reply-To: <6506286.203381405994602250.JavaMail.weblogic@epml18>
On Tue, Jul 22, 2014 at 02:03:22AM +0000, Eunbong Song wrote:
>
> In case of mips bigendian machine, put_unaligned writes bigendian bytes order.
> This is defined in arch/mips/include/asm/unaligned.h. So it's right use put_unaligned_le16 function instead of put_unaligned.
> This patch also fixes problem fail to mount zram ext4 partition with "zram: Decompression failed! err=-1, page=0" in mips bigendian machine.
Odd line wrapping :(
Anyway, is this a new problem? Or something that has always been there
in this compression function?
thanks,
greg k-h
prev parent reply other threads:[~2014-07-22 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 2:03 [PATCH] lib : lz4 using put_unaligned_le16 instead of put_unaligned Eunbong Song
2014-07-22 2:11 ` Greg KH [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=20140722021137.GD19215@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chanho.min@lge.com \
--cc=eunb.song@samsung.com \
--cc=linux-kernel@vger.kernel.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