From: "David S. Miller" <davem@redhat.com>
To: willy@debian.org
Cc: alan@lxorguk.ukuu.org.uk, rmk@arm.linux.org.uk, hugh@veritas.com,
akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] shmem missing cache flush
Date: Mon, 28 Oct 2002 06:26:08 -0800 (PST) [thread overview]
Message-ID: <20021028.062608.78045801.davem@redhat.com> (raw)
In-Reply-To: <20021028143226.N27461@parcelfarce.linux.theplanet.co.uk>
From: Matthew Wilcox <willy@debian.org>
Date: Mon, 28 Oct 2002 14:32:26 +0000
s/well maintained port/port that linus takes patches from regularly/
If you can't get purely arch/* include/asm-* patches to him,
that isn't my problem.
Yes, you might have to retransmit that patch 20/30 times over the
course of a few days depending upon how busy Linus is, just get over
it. :-)
What do you want to do about flush_icache_page? You want to change it
to flush_dcache_page at eviction time, and then we can purge that page
from our icache in update_mmu_cache?
That's the idea. The other idea is "well these particular call spots
really are special, so let's document flush_icache_page properly".
You may as well drop this hunk from the diff; our current tree doesn't
even have these functions; just:
static inline void
flush_page_to_ram(struct page *page)
{
}
I gave Alan a patch that applies to 2.5.44 as-is, that is the most
useful form of the patch.
If you code is different now, you or Alan can deal with the conflict
once it does arrise and your "other code" is in 2.5.x. For now it
isn't so it doesn't make any sense for me to patch against something
that isn't there :-)
next prev parent reply other threads:[~2002-10-28 14:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 18:26 [PATCH] shmem missing cache flush Matthew Wilcox
2002-10-16 23:57 ` Hugh Dickins
2002-10-16 23:58 ` David S. Miller
2002-10-17 0:19 ` Russell King
2002-10-17 0:16 ` David S. Miller
2002-10-21 15:04 ` Alan Cox
2002-10-21 15:21 ` David S. Miller
2002-10-21 16:12 ` Alan Cox
2002-10-28 14:10 ` David S. Miller
2002-10-28 14:32 ` Matthew Wilcox
2002-10-28 14:26 ` David S. Miller [this message]
2002-10-28 16:36 ` Matthew Wilcox
2002-10-28 16:55 ` David S. Miller
2002-10-28 17:06 ` Matthew Wilcox
2002-10-28 16:58 ` David S. Miller
2002-10-29 21:52 ` Matthew Wilcox
2002-10-28 17:08 ` Alan Cox
2002-10-28 16:52 ` Matthew Wilcox
2002-10-28 14:35 ` Hugh Dickins
2002-10-28 14:26 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 16:50 Manfred Spraul
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=20021028.062608.78045801.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=willy@debian.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