From: Eric Biggers <ebiggers3@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
jaegeuk@kernel.org, tytso@mit.edu, hch@infradead.org,
arnd@arndb.de, dedekind1@gmail.com,
linux-mtd@lists.infradead.org, adrian.hunter@intel.com,
linux-ext4@vger.kernel.org, ebiggers@google.com,
rdunlap@infradead.org, david@sigma-star.at
Subject: Re: [PATCH v2] fscrypt: Factor out bio specific functions
Date: Mon, 19 Dec 2016 14:40:29 -0800 [thread overview]
Message-ID: <20161219224029.GE37112@gmail.com> (raw)
In-Reply-To: <20161219112532.18863-1-richard@nod.at>
On Mon, Dec 19, 2016 at 12:25:32PM +0100, Richard Weinberger wrote:
> That way we can get rid of the direct dependency on CONFIG_BLOCK.
>
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Suggested-by: Christoph Hellwig <hch@infradead.org>
> Fixes: d475a507457b ("ubifs: Add skeleton for fscrypto")
> Signed-off-by: Richard Weinberger <richard@nod.at>
> ---
> Changes since v1:
> - Moved fscrypt_zeroout_range() also to bio.c
Reviewed-by: Eric Biggers <ebiggers@google.com>
Thanks,
Eric
next prev parent reply other threads:[~2016-12-19 22:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 10:50 [PATCH] fscrypt: Factor out bio specific functions Richard Weinberger
2016-12-16 15:37 ` David Gstir
2016-12-16 20:48 ` Richard Weinberger
2016-12-16 22:14 ` Eric Biggers
2016-12-16 22:18 ` Richard Weinberger
2016-12-19 10:39 ` Christoph Hellwig
2016-12-19 11:25 ` [PATCH v2] " Richard Weinberger
2016-12-19 22:40 ` Eric Biggers [this message]
2016-12-20 5:56 ` Christoph Hellwig
2016-12-20 6:42 ` David Gstir
2017-01-01 21:47 ` Theodore Ts'o
2017-01-03 9:49 ` Richard Weinberger
2017-01-03 14:28 ` Theodore Ts'o
2017-01-04 20:10 ` Eric Biggers
2017-01-04 22:52 ` Richard Weinberger
2017-01-07 19:24 ` Theodore Ts'o
2017-01-07 22:40 ` Richard Weinberger
2017-01-09 13:33 ` Christoph Hellwig
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=20161219224029.GE37112@gmail.com \
--to=ebiggers3@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=david@sigma-star.at \
--cc=dedekind1@gmail.com \
--cc=ebiggers@google.com \
--cc=hch@infradead.org \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=tytso@mit.edu \
/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).