From: Carmeli Tamir <carmeli.tamir@gmail.com>
To: carmeli.tamir@gmail.com, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Refactor file_systems to use the kernel's list
Date: Sat, 4 May 2019 05:45:47 -0400 [thread overview]
Message-ID: <20190504094549.10021-1-carmeli.tamir@gmail.com> (raw)
struct file_system_type defines a next field which is used to link the file_system_type structs registered to the kernel. This patch set replaces the propietry linked list implementation with the kernel's list.h.
This change makes clearer interfaces and code (e.g. the change in register_filesystem and find_filesystem), and eliminates unnecessary usage of * and & operators.
Tested by comparing the lists in /proc/filesystems.
Carmeli Tamir (2):
Use list.h instead of file_system_type next
Changed unsigned param type to unsigned int
fs/filesystems.c | 69 ++++++++++++++++++++++++----------------------
include/linux/fs.h | 2 +-
2 files changed, 37 insertions(+), 34 deletions(-)
--
2.19.1
next reply other threads:[~2019-05-04 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 9:45 Carmeli Tamir [this message]
2019-05-04 9:45 ` [PATCH 1/2] Use list.h instead of file_system_type next Carmeli Tamir
2019-05-04 13:20 ` Al Viro
2019-05-04 13:45 ` Matthew Wilcox
2019-05-05 18:25 ` Tamir Carmeli
2019-05-06 2:49 ` Matthew Wilcox
2019-05-06 15:16 ` kbuild test robot
2019-05-06 17:33 ` kbuild test robot
2019-05-04 9:45 ` [PATCH 2/2] Changed unsigned param type to unsigned int Carmeli Tamir
[not found] <20190504094212.9945-1-carmeli.tamir@gmail.com>
2019-05-04 9:42 ` [PATCH 0/2] Refactor file_systems to use the kernel's list Carmeli Tamir
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=20190504094549.10021-1-carmeli.tamir@gmail.com \
--to=carmeli.tamir@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).