From: Theodore Ts'o <tytso@mit.edu>
To: Richard Weinberger <richard@nod.at>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
jaegeuk@kernel.org, tytso@mit.ed, ebiggers@google.com,
david@sigma-star.at
Subject: Re: [PATCH] fscrypt: properly declare on-stack completion
Date: Mon, 6 Feb 2017 23:21:23 -0500 [thread overview]
Message-ID: <20170207042123.htwji5lsdtykkskr@thunk.org> (raw)
In-Reply-To: <20170201203209.17710-1-richard@nod.at>
On Wed, Feb 01, 2017 at 09:32:09PM +0100, Richard Weinberger wrote:
> When a completion is declared on-stack we have to use
> COMPLETION_INITIALIZER_ONSTACK().
>
> Fixes: 0b81d07790726 ("fs crypto: move per-file encryption from f2fs
> tree to fs/crypto")
> Signed-off-by: Richard Weinberger <richard@nod.at>
Thanks, applied.
- Ted
prev parent reply other threads:[~2017-02-07 4:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 20:32 [PATCH] fscrypt: properly declare on-stack completion Richard Weinberger
2017-02-01 20:34 ` Richard Weinberger
2017-02-07 4:21 ` Theodore Ts'o [this message]
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=20170207042123.htwji5lsdtykkskr@thunk.org \
--to=tytso@mit.edu \
--cc=david@sigma-star.at \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=tytso@mit.ed \
/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).