On Thu, Nov 01, 2018 at 05:02:36PM -0700, Daniel Walker wrote: > > > > On Thu, Nov 01, 2018 at 03:56:03PM -0700, Nikunj Kela wrote: > > This patch allows the endianness of the JFSS2 filesystem to be > > specified by config options. > > > > It defaults to native-endian (the previously hard-coded option). > > > > Some architectures benefit from having a single known endianness > > of JFFS2 filesystem (for data, not executables) independent of the > > endianness of the processor (ARM processors can be switched to either > > endianness at run-time). > > > > > The description is pretty sad .. We have a product which we released that uses > JFFS2, and that product was release with a kernel in one endianness. Then later > on we decided to change the endianness and now we're stuck with a JFFS2 > partition that has the wrong endiannes, in a released product. This patch allows > us to set the endianness to something different from the architecture setting. > > So there a significant use case for the change, at least for Cisco. FWIW, can't we detect it at mount time, as e.g. UFS does? ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/