linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	jaegeuk@kernel.org, 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: Sat, 7 Jan 2017 14:24:06 -0500	[thread overview]
Message-ID: <20170107192406.56p7ppbdfkjii4vy@thunk.org> (raw)
In-Reply-To: <20170104201043.GA21696@gmail.com>

On Wed, Jan 04, 2017 at 12:10:43PM -0800, Eric Biggers wrote:
> 
> I thought you're supposed to be able to build the kernel no matter how it's
> configured.  If this patch is really too large for 4.10 then perhaps we should
> make FS_ENCRYPTION select CONFIG_BLOCK instead?

We already have FS_ENCRYPTIOn depending on BLOCK, so this is *not*
fixing a build break.

Given that, it's a bit harder to claim this is a must-have bug fix for
the stable branch?

						- Ted

  parent reply	other threads:[~2017-01-07 19:24 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
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 [this message]
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=20170107192406.56p7ppbdfkjii4vy@thunk.org \
    --to=tytso@mit.edu \
    --cc=adrian.hunter@intel.com \
    --cc=arnd@arndb.de \
    --cc=david@sigma-star.at \
    --cc=dedekind1@gmail.com \
    --cc=ebiggers3@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 \
    /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).