From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] arm: mm: fix dcache flush logic for compound high pages
Date: Mon, 16 Dec 2013 15:54:04 +0000 [thread overview]
Message-ID: <20131216155403.GC20193@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1387206223-1670-1-git-send-email-steve.capper@linaro.org>
On Mon, Dec 16, 2013 at 03:03:43PM +0000, Steve Capper wrote:
> When given a compound high page, __flush_dcache_page will only flush
> the first page of the compound page repeatedly rather than the entire
> set of constituent pages.
>
> This patch corrects the logic such that all constituent pages are now
> flushed.
Since this probably wants to go to -stable, it's worth mentioning the commit
which introduced it in the commit text.
> Signed-off-by: Steve Capper <steve.capper@linaro.org>
> ---
> V2: style change use page + i rather than separate struct *cpage
> ---
Acked-by: Will Deacon <will.deacon@arm.com>
Cheers Steve.
Will
next prev parent reply other threads:[~2013-12-16 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 15:03 [PATCH V2] arm: mm: fix dcache flush logic for compound high pages Steve Capper
2013-12-16 15:54 ` Will Deacon [this message]
2013-12-16 16:28 ` Steve Capper
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=20131216155403.GC20193@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.