From: Christoph Hellwig <hch@infradead.org> To: Nicolas Pitre <nicolas.pitre@linaro.org> Cc: Alexander Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@infradead.org>, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org, Chris Brandt <Chris.Brandt@renesas.com> Subject: Re: [PATCH v5 0/5] cramfs refresh for embedded usage Date: Thu, 5 Oct 2017 23:39:19 -0700 [thread overview] Message-ID: <20171006063919.GA16556@infradead.org> (raw) In-Reply-To: <20171006024531.8885-1-nicolas.pitre@linaro.org> This is still missing a proper API for accessing the file system, as said before specifying a physical address in the mount command line is a an absolute non-no. Either work with the mtd folks to get the mtd core down to an absolute minimum suitable for you, or figure out a way to specify fs nodes through DT or similar.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org> To: Nicolas Pitre <nicolas.pitre@linaro.org> Cc: Alexander Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@infradead.org>, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org, Chris Brandt <Chris.Brandt@renesas.com> Subject: Re: [PATCH v5 0/5] cramfs refresh for embedded usage Date: Thu, 5 Oct 2017 23:39:19 -0700 [thread overview] Message-ID: <20171006063919.GA16556@infradead.org> (raw) In-Reply-To: <20171006024531.8885-1-nicolas.pitre@linaro.org> This is still missing a proper API for accessing the file system, as said before specifying a physical address in the mount command line is a an absolute non-no. Either work with the mtd folks to get the mtd core down to an absolute minimum suitable for you, or figure out a way to specify fs nodes through DT or similar. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-10-06 6:39 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-06 2:45 [PATCH v5 0/5] cramfs refresh for embedded usage Nicolas Pitre 2017-10-06 2:45 ` Nicolas Pitre 2017-10-06 2:45 ` [PATCH v5 1/5] cramfs: direct memory access support Nicolas Pitre 2017-10-06 2:45 ` Nicolas Pitre 2017-10-06 2:45 ` [PATCH v5 2/5] cramfs: make cramfs_physmem usable as root fs Nicolas Pitre 2017-10-06 2:45 ` Nicolas Pitre 2017-10-06 2:45 ` [PATCH v5 3/5] cramfs: implement uncompressed and arbitrary data block positioning Nicolas Pitre 2017-10-06 2:45 ` Nicolas Pitre 2017-10-06 2:45 ` [PATCH v5 4/5] cramfs: add mmap support Nicolas Pitre 2017-10-06 2:45 ` Nicolas Pitre 2017-10-06 7:00 ` Christoph Hellwig 2017-10-06 7:00 ` Christoph Hellwig 2017-10-06 17:41 ` Nicolas Pitre 2017-10-06 17:41 ` Nicolas Pitre 2017-10-06 2:45 ` [PATCH v5 5/5] cramfs: rehabilitate it Nicolas Pitre 2017-10-06 2:45 ` Nicolas Pitre 2017-10-06 6:39 ` Christoph Hellwig [this message] 2017-10-06 6:39 ` [PATCH v5 0/5] cramfs refresh for embedded usage Christoph Hellwig 2017-10-06 16:07 ` Chris Brandt 2017-10-06 16:07 ` Chris Brandt 2017-10-06 16:30 ` Nicolas Pitre 2017-10-06 16:30 ` Nicolas Pitre
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=20171006063919.GA16556@infradead.org \ --to=hch@infradead.org \ --cc=Chris.Brandt@renesas.com \ --cc=linux-embedded@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=nicolas.pitre@linaro.org \ --cc=viro@zeniv.linux.org.uk \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.