From: domen@coderock.org
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: linux-fsdevel@vger.kernel.org,
Maximilian Attems <janitor@sternwelten.at>,
domen@coderock.org
Subject: [patch 1/7] list_for_each_entry: fs-namespace.c
Date: Mon, 20 Jun 2005 23:57:00 +0200 [thread overview]
Message-ID: <20050620215700.432387000@nd47.coderock.org> (raw)
[-- Attachment #1: list-for-each-entry-fs_namespace.patch --]
[-- Type: text/plain, Size: 1137 bytes --]
From: Domen Puncer <domen@coderock.org>
Make code more readable with list_for_each_entry.
Compile tested.
Signed-off-by: Domen Puncer <domen@coderock.org>
Signed-off-by: Maximilian Attems <janitor@sternwelten.at>
Signed-off-by: Domen Puncer <domen@coderock.org>
---
namespace.c | 4 +---
1 files changed, 1 insertion(+), 3 deletions(-)
Index: quilt/fs/namespace.c
===================================================================
--- quilt.orig/fs/namespace.c
+++ quilt/fs/namespace.c
@@ -536,7 +536,6 @@ lives_below_in_same_fs(struct dentry *d,
static struct vfsmount *copy_tree(struct vfsmount *mnt, struct dentry *dentry)
{
struct vfsmount *res, *p, *q, *r, *s;
- struct list_head *h;
struct nameidata nd;
res = q = clone_mnt(mnt, dentry);
@@ -545,8 +544,7 @@ static struct vfsmount *copy_tree(struct
q->mnt_mountpoint = mnt->mnt_mountpoint;
p = mnt;
- for (h = mnt->mnt_mounts.next; h != &mnt->mnt_mounts; h = h->next) {
- r = list_entry(h, struct vfsmount, mnt_child);
+ list_for_each_entry(r, &mnt->mnt_mounts, mnt_child) {
if (!lives_below_in_same_fs(r->mnt_mountpoint, dentry))
continue;
--
next reply other threads:[~2005-06-20 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 21:57 domen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-06 10:37 [patch 1/7] list_for_each_entry: fs-namespace.c domen
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=20050620215700.432387000@nd47.coderock.org \
--to=domen@coderock.org \
--cc=janitor@sternwelten.at \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.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).