From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: cache flushing LoUIS API v2
Date: Fri, 28 Sep 2012 15:21:40 +0100 [thread overview]
Message-ID: <20120928142140.GD30058@e102568-lin.cambridge.arm.com> (raw)
In-Reply-To: <20120928131530.GG7916@n2100.arm.linux.org.uk>
On Fri, Sep 28, 2012 at 02:15:30PM +0100, Russell King - ARM Linux wrote:
> On Fri, Sep 28, 2012 at 02:12:54PM +0100, Lorenzo Pieralisi wrote:
> > Ok, understood, sorry. What's the best way forward then ?
> >
> > Should I add the fix for xscale and feroceon to your patch system ?
>
> That's one solution, and probably the best as it means less commits in
> the end.
Done, 7542/1, applied and tested on top of your current devel-stable.
It does solve linux-next build issues for Orion5, Kirkwood and mv78xx0
caused by missing feroceon_range_flush_kern_cache_louis alias.
My apologies, thanks.
Lorenzo
prev parent reply other threads:[~2012-09-28 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 9:21 [GIT PULL] ARM: cache flushing LoUIS API v2 Lorenzo Pieralisi
2012-09-28 12:54 ` Russell King - ARM Linux
2012-09-28 13:12 ` Lorenzo Pieralisi
2012-09-28 13:15 ` Russell King - ARM Linux
2012-09-28 14:21 ` Lorenzo Pieralisi [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=20120928142140.GD30058@e102568-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox