From: domen@coderock.org
To: jack@suse.cz
Cc: linux-kernel@vger.kernel.org,
Maximilian Attems <janitor@sternwelten.at>,
domen@coderock.org
Subject: [patch 1/1] list_for_each_entry: fs-dquot.c
Date: Mon, 20 Jun 2005 23:56:54 +0200 [thread overview]
Message-ID: <20050620215654.202069000@nd47.coderock.org> (raw)
[-- Attachment #1: list-for-each-entry-safe-fs_dquot.patch --]
[-- Type: text/plain, Size: 985 bytes --]
From: Domen Puncer <domen@coderock.org>
Make code more readable with list_for_each_entry_safe.
Signed-off-by: Domen Puncer <domen@coderock.org>
Signed-off-by: Maximilian Attems <janitor@sternwelten.at>
Signed-off-by: Domen Puncer <domen@coderock.org>
---
dquot.c | 7 ++-----
1 files changed, 2 insertions(+), 5 deletions(-)
Index: quilt/fs/dquot.c
===================================================================
--- quilt.orig/fs/dquot.c
+++ quilt/fs/dquot.c
@@ -409,13 +409,10 @@ out_dqlock:
* for this sb+type at all. */
static void invalidate_dquots(struct super_block *sb, int type)
{
- struct dquot *dquot;
- struct list_head *head;
+ struct dquot *dquot, *tmp;
spin_lock(&dq_list_lock);
- for (head = inuse_list.next; head != &inuse_list;) {
- dquot = list_entry(head, struct dquot, dq_inuse);
- head = head->next;
+ list_for_each_entry_safe(dquot, tmp, &inuse_list, dq_inuse) {
if (dquot->dq_sb != sb)
continue;
if (dquot->dq_type != type)
--
next reply other threads:[~2005-06-21 5:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 21:56 domen [this message]
2005-06-23 8:44 ` [patch 1/1] list_for_each_entry: fs-dquot.c Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2005-01-10 18:42 domen
2005-01-11 14:34 ` Jan Kara
2005-01-11 15:32 ` Domen Puncer
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=20050620215654.202069000@nd47.coderock.org \
--to=domen@coderock.org \
--cc=jack@suse.cz \
--cc=janitor@sternwelten.at \
--cc=linux-kernel@vger.kernel.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 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.