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 v6 3/4] cramfs: add mmap support
Date: Fri, 13 Oct 2017 00:31:01 -0700 [thread overview]
Message-ID: <20171013073101.GJ9105@infradead.org> (raw)
In-Reply-To: <20171012061613.28705-4-nicolas.pitre@linaro.org>
As said before I'm no big fan of all the debug chatter, but the rest
looks fine, so:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2017-10-13 7:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 6:16 [PATCH v6 0/4] cramfs refresh for embedded usage Nicolas Pitre
2017-10-12 6:16 ` [PATCH v6 1/4] cramfs: direct memory access support Nicolas Pitre
2017-10-12 17:03 ` Chris Brandt
2017-10-13 1:20 ` Nicolas Pitre
2017-10-13 7:30 ` Christoph Hellwig
2017-10-13 17:29 ` Al Viro
2017-10-13 17:39 ` Nicolas Pitre
2017-10-13 17:52 ` Al Viro
2017-10-13 18:18 ` Nicolas Pitre
2017-10-13 20:09 ` Nicolas Pitre
2017-10-14 0:31 ` Al Viro
2017-10-14 2:25 ` Nicolas Pitre
2017-10-14 2:37 ` Nicolas Pitre
2017-10-12 6:16 ` [PATCH v6 2/4] cramfs: implement uncompressed and arbitrary data block positioning Nicolas Pitre
2017-10-12 6:16 ` [PATCH v6 3/4] cramfs: add mmap support Nicolas Pitre
2017-10-13 7:31 ` Christoph Hellwig [this message]
2017-10-12 6:16 ` [PATCH v6 4/4] cramfs: rehabilitate it 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=20171013073101.GJ9105@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: 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;
as well as URLs for NNTP newsgroup(s).