From: domen@coderock.org
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: linux-fsdevel@vger.kernel.org, domen@coderock.org,
janitor@sternwelten.at
Subject: [patch 1/7] list_for_each_entry: fs-namespace.c
Date: Sun, 06 Mar 2005 11:37:30 +0100 [thread overview]
Message-ID: <20050306103731.B895E1F208@trashy.coderock.org> (raw)
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>
---
kj-domen/fs/namespace.c | 4 +---
1 files changed, 1 insertion(+), 3 deletions(-)
diff -puN fs/namespace.c~list-for-each-entry-fs_namespace fs/namespace.c
--- kj/fs/namespace.c~list-for-each-entry-fs_namespace 2005-03-05 16:09:03.000000000 +0100
+++ kj-domen/fs/namespace.c 2005-03-05 16:09:03.000000000 +0100
@@ -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-03-06 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 10:37 domen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-20 21:57 [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=20050306103731.B895E1F208@trashy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.