From: Martin Waitz <tali@admingilde.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: David Howells <dhowells@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] cachefs: possible cleanups
Date: Tue, 4 Jan 2005 09:49:08 +0100 [thread overview]
Message-ID: <20050104084907.GA10016@admingilde.org> (raw)
In-Reply-To: <20050103235340.GS2980@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
hoi :)
On Tue, Jan 04, 2005 at 12:53:40AM +0100, Adrian Bunk wrote:
> The patch below contains the following possible cleanups:
> - misc.c: #if 0 the unused global function __cachefs_page_get_private
it looks like this function should be removed, it is a duplicate of
__fscache_page_get_private in fs/fscache/page.c (from before the fscache split)
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-01-04 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 23:53 [-mm patch] cachefs: possible cleanups Adrian Bunk
2005-01-04 8:49 ` Martin Waitz [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=20050104084907.GA10016@admingilde.org \
--to=tali@admingilde.org \
--cc=bunk@stusta.de \
--cc=dhowells@redhat.com \
--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.