public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-fscrypt@vger.kernel.org,
	Artem Bityutskiy <dedekind1@gmail.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH v2 0/5] ubifs: switch to new fscrypt helper functions
Date: Fri, 05 Jan 2018 23:11:00 +0100	[thread overview]
Message-ID: <2774377.VZm18AqBqi@blindfold> (raw)
In-Reply-To: <20180105183744.GA44929@gmail.com>

Eric,

Am Freitag, 5. Januar 2018, 19:37:44 CET schrieb Eric Biggers:
> On Wed, Nov 29, 2017 at 12:43:12PM -0800, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> > 
> > This series switches ubifs to use the fscrypt helper functions for
> > open/link/rename/lookup/setattr introduced in v4.15.
> > 
> > These patches were originally sent in "[PATCH 00/25] fscrypt: add some
> > higher-level helper functions".  I've rebased them onto v4.15-rc1.
> > 
> > Eric Biggers (5):
> >   ubifs: switch to fscrypt_file_open()
> >   ubifs: switch to fscrypt_prepare_link()
> >   ubifs: switch to fscrypt_prepare_rename()
> >   ubifs: switch to fscrypt_prepare_lookup()
> >   ubifs: switch to fscrypt_prepare_setattr()
> >  
> >  fs/ubifs/dir.c  | 43 +++++++++++++------------------------------
> >  fs/ubifs/file.c | 41 ++++-------------------------------------
> >  2 files changed, 17 insertions(+), 67 deletions(-)
> 
> Richard, can you take these for UBIFS for v4.16?

Yes. Thanks a lot for cleaning this up.

Thanks,
//richard

  reply	other threads:[~2018-01-05 22:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 20:43 [PATCH v2 0/5] ubifs: switch to new fscrypt helper functions Eric Biggers
2017-11-29 20:43 ` [PATCH v2 1/5] ubifs: switch to fscrypt_file_open() Eric Biggers
2017-11-29 20:43 ` [PATCH v2 2/5] ubifs: switch to fscrypt_prepare_link() Eric Biggers
2017-11-29 20:43 ` [PATCH v2 3/5] ubifs: switch to fscrypt_prepare_rename() Eric Biggers
2017-11-29 20:43 ` [PATCH v2 4/5] ubifs: switch to fscrypt_prepare_lookup() Eric Biggers
2017-11-29 20:43 ` [PATCH v2 5/5] ubifs: switch to fscrypt_prepare_setattr() Eric Biggers
2018-01-05 18:37 ` [PATCH v2 0/5] ubifs: switch to new fscrypt helper functions Eric Biggers
2018-01-05 22:11   ` Richard Weinberger [this message]
2018-01-17 21:12     ` Richard Weinberger
2018-01-17 21:23       ` Eric Biggers
2018-01-17 21:36         ` Richard Weinberger
2018-01-17 23:44           ` Eric Biggers

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=2774377.VZm18AqBqi@blindfold \
    --to=richard@nod.at \
    --cc=adrian.hunter@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    /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