From: "Jörn Engel" <joern@logfs.org>
To: Chris Malley <mail@chrismalley.co.uk>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [MTD] CORE: Use list_for_each_entry[_safe] where appropriate (2nd attempt)
Date: Mon, 19 May 2008 13:38:58 +0200 [thread overview]
Message-ID: <20080519113858.GB32679@logfs.org> (raw)
In-Reply-To: <1211139433.19435.19.camel@localhost>
On Sun, 18 May 2008 20:37:13 +0100, Chris Malley wrote:
>
> + list_for_each_entry(tr, &blktrans_majors, list) {
> tr->add_mtd(tr, mtd);
> }
In a couple of places like this the loop body became a single line. So
you could remove the braces as well, while at it.
> diff --git a/drivers/mtd/mtdpart.c b/drivers/mtd/mtdpart.c
> index 07c7011..b7847f2 100644
> --- a/drivers/mtd/mtdpart.c
> +++ b/drivers/mtd/mtdpart.c
> @@ -302,20 +302,14 @@ static int part_block_markbad (struct mtd_info *mtd, loff_t ofs)
>
> int del_mtd_partitions(struct mtd_info *master)
> {
> - struct list_head *node;
> - struct mtd_part *slave;
> + struct mtd_part *slave, *safe;
"next" seems a bit better than "safe".
Rest looks fine to me. So I leave it up to you whether to add those
trivial cosmetics or just leave the patch as-is. Either way, it is an
improvement. Also, having dwmw2 on Cc: improves the chances of this
patch not being ignored. ;)
Reviewed-By: Joern Engel <joern@logfs.org>
Jörn
--
Victory in war is not repetitious.
-- Sun Tzu
next prev parent reply other threads:[~2008-05-19 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 17:54 [PATCH] [MTD] CORE: Use list_for_each_entry[_safe] where appropriate Chris Malley
2008-05-17 19:49 ` Jörn Engel
2008-05-17 20:08 ` Chris Malley
2008-05-18 19:37 ` [PATCH] [MTD] CORE: Use list_for_each_entry[_safe] where appropriate (2nd attempt) Chris Malley
2008-05-19 11:38 ` Jörn Engel [this message]
2008-05-19 19:11 ` [PATCH] [MTD] CORE: Use list_for_each_entry[_safe] where appropriate (3rd attempt) Chris Malley
2008-05-19 19:27 ` Jörn Engel
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=20080519113858.GB32679@logfs.org \
--to=joern@logfs.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mail@chrismalley.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