From: heechul Yun <heechul.yun@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: [patch] Endian problem of nftl_format and nftldump
Date: Fri, 17 Dec 2004 11:30:31 +0900 [thread overview]
Message-ID: <f8521c9904121618302afe15e4@mail.gmail.com> (raw)
Hello
It seems that both programs should #include <endian.h>.
If not, the following code can cause problem as it becomes always true.
#if __BYTE_ORDER == __BIG_ENDIAN
...
Regards,
Heechul.
===========
Heechul Yun
Digital Media Research Center
Samsung Electronics
Tel: +82-31-200-9334
reply other threads:[~2004-12-17 2:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f8521c9904121618302afe15e4@mail.gmail.com \
--to=heechul.yun@gmail.com \
--cc=linux-mtd@lists.infradead.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