From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mm: enable L1 prefetch on Cortex-A9
Date: Mon, 15 Jun 2015 17:15:53 +0200 [thread overview]
Message-ID: <20150615171553.53b5c396@free-electrons.com> (raw)
In-Reply-To: <20150615150522.GN7557@n2100.arm.linux.org.uk>
Hello,
On Mon, 15 Jun 2015 16:05:22 +0100, Russell King - ARM Linux wrote:
> > However, can you consider my "ARM: smp_scu: enable coherent speculative
> > linefills", which has been sent almost three months ago:
> >
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/332106.html
>
> I looked at that, and decided I didn't have enough information to know
> whether that's a good idea to apply or not for all the different variants
> we have out there. It's something that needs to be merged early in the
> cycle to give it enough time to be (hopefully) tested by people.
>
> A lot of these "enable optimisation X" patches need to go through that
> treatment.
Makes perfect sense. Can we get these "enable optimization X" patches
merged early enough in the 4.3 cycle, i.e right after 4.2-rc1 is
released?
Thanks a lot,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-15 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 11:52 [PATCH] ARM: mm: enable L1 prefetch on Cortex-A9 Thomas Petazzoni
2015-06-15 10:42 ` Dirk Behme
2015-06-15 14:56 ` Thomas Petazzoni
2015-06-15 11:11 ` Russell King - ARM Linux
2015-06-15 14:57 ` Thomas Petazzoni
2015-06-15 15:05 ` Russell King - ARM Linux
2015-06-15 15:15 ` Thomas Petazzoni [this message]
2015-06-16 13:47 ` Rob Herring
2015-06-16 14:10 ` Thomas Petazzoni
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=20150615171553.53b5c396@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).