public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
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 (3rd attempt)
Date: Mon, 19 May 2008 21:27:39 +0200	[thread overview]
Message-ID: <20080519192739.GC32679@logfs.org> (raw)
In-Reply-To: <1211224310.7343.2.camel@localhost>

On Mon, 19 May 2008 20:11:50 +0100, Chris Malley wrote:
> 
> [MTD] CORE: Use list_for_each_entry[_safe] where appropriate.
> 
> Janitorial work to remove temporary pointers and make some functions a bit
> more readable.
> 
> Signed-off-by: Chris Malley <mail@chrismalley.co.uk>
> Reviewed-By: Joern Engel <joern@logfs.org>

Excellent, thanks!

Jörn

-- 
Data dominates. If you've chosen the right data structures and organized
things well, the algorithms will almost always be self-evident. Data
structures, not algorithms, are central to programming.
-- Rob Pike

      reply	other threads:[~2008-05-19 19:27 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
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 [this message]

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=20080519192739.GC32679@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