From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-mtd@lists.infradead.org
Cc: Richard Weinberger <richard@nod.at>,
linux-fscrypt@vger.kernel.org,
"Theodore Y . Ts'o" <tytso@mit.edu>,
kernel@pengutronix.de, Sascha Hauer <s.hauer@pengutronix.de>
Subject: [PATCH 0/2] ubifs: Get rid of some ifdefs
Date: Tue, 26 Mar 2019 08:52:30 +0100 [thread overview]
Message-ID: <20190326075232.11717-1-s.hauer@pengutronix.de> (raw)
This series gets rid of some ifdefs in the UBFIS code. fscrypt folks are
on Cc because I introduce a static inline wrapper for setting the
super_block.s_cop ops so that filesystems do not have to add a
#ifdef CONFIG_FS_ENCRYPTION around setting the ops. I can do this as an
extra patch if that's desired.
Sascha
Sascha Hauer (2):
ubifs: Remove #ifdef around CONFIG_FS_ENCRYPTION
ubifs: Remove ifdefs around CONFIG_UBIFS_ATIME_SUPPORT
fs/ubifs/dir.c | 2 --
fs/ubifs/file.c | 16 +++++++---------
fs/ubifs/ioctl.c | 11 +----------
fs/ubifs/sb.c | 7 ++++---
fs/ubifs/super.c | 20 +++++++++-----------
fs/ubifs/ubifs.h | 2 --
include/linux/fscrypt.h | 11 +++++++++++
7 files changed, 32 insertions(+), 37 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-26 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 7:52 Sascha Hauer [this message]
2019-03-26 7:52 ` [PATCH 1/2] ubifs: Remove #ifdef around CONFIG_FS_ENCRYPTION Sascha Hauer
2019-05-08 3:19 ` Eric Biggers
2019-05-08 6:49 ` Richard Weinberger
2019-05-13 19:56 ` Eric Biggers
2019-05-13 21:39 ` Richard Weinberger
2019-03-26 7:52 ` [PATCH 2/2] ubifs: Remove ifdefs around CONFIG_UBIFS_ATIME_SUPPORT Sascha Hauer
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=20190326075232.11717-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-mtd@lists.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).