From: "Pekka J Enberg" <penberg@cs.helsinki.fi>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Chris Wright <chrisw@osdl.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: isofs: unobfuscate rock.c
Date: Tue, 29 Mar 2005 09:22:04 +0300 [thread overview]
Message-ID: <courier.4248F40C.00006DA4@courier.cs.helsinki.fi> (raw)
In-Reply-To: <20050328223048.GA2741@pclin040.win.tue.nl>
Hi Andries,
Andries Brouwer writes:
> Good! When Linus asked I audited rock.c and also did rather similar polishing -
> it happens automatically if one looks at this code. But it seems everybody is
> doing this right now, so I must wait a few weeks and see what got into Linus'
> tree. Linus plugged many but not all holes. (Maybe you did more?)
I didn't fix anything. I tried to be very careful about preserving the
current logic while making it more readable so I could find bugs :-).
Pekka
prev parent reply other threads:[~2005-03-29 6:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 17:41 [PATCH 0/9] " Pekka Enberg
2005-03-28 17:41 ` [PATCH 1/9] isofs: indent rock.c Pekka Enberg
2005-03-28 17:41 ` [PATCH 2/9] isofs: inline macros in rock.c Pekka Enberg
2005-03-28 17:41 ` [PATCH 3/9] " Pekka Enberg
2005-03-28 17:41 ` [PATCH 4/9] " Pekka Enberg
2005-03-28 17:41 ` [PATCH 5/9] isofs: convert macro to function " Pekka Enberg
2005-03-28 17:42 ` [PATCH 6/9] " Pekka Enberg
2005-03-28 17:42 ` [PATCH 7/9] isofs: extract zisofs parsing to function Pekka Enberg
2005-03-28 17:42 ` [PATCH 8/9] isofs: remove redundant kfree checks from rock Pekka Enberg
2005-03-28 17:42 ` [PATCH 9/9] isofs: clean up rock.c Pekka Enberg
2005-03-28 20:02 ` [PATCH 0/9] isofs: unobfuscate rock.c Chris Wright
2005-03-28 22:30 ` Andries Brouwer
2005-03-28 22:46 ` Chris Wright
2005-03-29 6:22 ` Pekka J Enberg [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=courier.4248F40C.00006DA4@courier.cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=aebr@win.tue.nl \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®