From: Richard Weinberger <richard@nod.at>
To: Daniel Walker <danielwa@cisco.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
nkela@cisco.com, xe-linux-external@cisco.com,
LKML <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org, Rod Whitby <rod@whitby.id.au>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] Make JFFS2 endianness configurable
Date: Fri, 02 Nov 2018 22:22:53 +0100 [thread overview]
Message-ID: <2265901.Da3O5o3T4q@blindfold> (raw)
In-Reply-To: <20181102211444.nqqqbd4w5diyqrfw@zorba>
Am Freitag, 2. November 2018, 22:14:44 CET schrieb Daniel Walker:
> > Make it a mount option and store the endianness mode in the super block.
>
> It's actually a mkfs option currently. I'm not sure how that factors in,
>
> from the mkfs.jffs2 man page,
>
> -l, --little-endian
> Create a little-endian JFFS2 image. Default is to make an image with the same endianness as the host.
>
> -b, --big-endian
> Create a big-endian JFFS2 image. Default is to make an image with the same endianness as the host.
As long this setting is not stored in the filesystem itself, it is useless.
IIRC it just controls the endianness setting for mkfs.jffs2's
t32() and t16() macros.
That's why I think of a mount option like "force_endian=".
Thanks,
//richard
next prev parent reply other threads:[~2018-11-02 21:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 22:56 [PATCH] Make JFFS2 endianness configurable Nikunj Kela
2018-11-02 0:02 ` Daniel Walker
2018-11-02 0:34 ` Al Viro
2018-11-02 14:04 ` Daniel Walker
2018-11-02 20:15 ` Richard Weinberger
2018-11-02 21:14 ` Daniel Walker
2018-11-02 21:22 ` Richard Weinberger [this message]
2018-11-07 1:09 ` Nikunj Kela (nkela)
2018-11-02 8:45 ` Joakim Tjernlund
2018-11-02 9:28 ` Richard Weinberger
-- strict thread matches above, loose matches on Subject: below --
2006-01-12 20:18 [PATCH]: " Rod Whitby
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=2265901.Da3O5o3T4q@blindfold \
--to=richard@nod.at \
--cc=danielwa@cisco.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nkela@cisco.com \
--cc=richard.weinberger@gmail.com \
--cc=rod@whitby.id.au \
--cc=viro@zeniv.linux.org.uk \
--cc=xe-linux-external@cisco.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