From: "David S. Miller" <davem@redhat.com>
To: paulus@samba.org
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: drivers/block/rd.c compile error
Date: Thu, 10 Oct 2002 06:25:41 -0700 (PDT) [thread overview]
Message-ID: <20021010.062541.03157158.davem@redhat.com> (raw)
In-Reply-To: <15781.7200.98489.515226@nanango.paulus.ozlabs.org>
From: Paul Mackerras <paulus@samba.org>
Date: Thu, 10 Oct 2002 16:20:16 +1000 (EST)
What was the change trying to achieve? What was wrong with
flush_dcache_page(page)?
The wrong page was being passed to flush_dcache_page(). 'page'
is not what is being written to with kernel cpu stores.
The real problem is that Alan stuck the raw 2.4.x version of
the fix into 2.5, it compiled on x86 because the argument
doesn't get evaluated, so we just need to fix it up :-)
And as Andrew stated, there are many other problems with the
ramdisk driver in 2.5.x
prev parent reply other threads:[~2002-10-10 13:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 6:20 drivers/block/rd.c compile error Paul Mackerras
2002-10-10 7:09 ` Andrew Morton
2002-10-10 13:25 ` David S. Miller [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=20021010.062541.03157158.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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