From: Adrian Bunk <bunk@stusta.de>
To: Hans Reiser <reiser@namesys.com>
Cc: reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] fs/reiser4/: misc cleanups
Date: Sat, 7 Jan 2006 01:12:09 +0100 [thread overview]
Message-ID: <20060107001209.GF3774@stusta.de> (raw)
In-Reply-To: <43BF0629.2030705@namesys.com>
On Fri, Jan 06, 2006 at 04:07:05PM -0800, Hans Reiser wrote:
> Adrian Bunk wrote:
>
> >This patch makes some needlessly global code static and #ifdef's some
> >unused code away.
> >
> >
> >Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> >
> Did we lose this patch from our patch process, or is this more cleanups
> from you?
>...
These are more cleanups.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-01-07 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 22:39 [-mm patch] fs/reiser4/: misc cleanups Adrian Bunk
2006-01-07 0:07 ` Hans Reiser
2006-01-07 0:12 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-15 21:55 Adrian Bunk
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=20060107001209.GF3774@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-dev@namesys.com \
/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