From: Catalin Marinas <catalin.marinas@arm.com>
To: naveen yadav <yad.naveen@gmail.com>
Cc: Greg KH <greg@kroah.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Long term stable kernel seletion (3.0)
Date: Fri, 27 Jan 2012 11:24:34 +0000 [thread overview]
Message-ID: <20120127112434.GA7757@arm.com> (raw)
In-Reply-To: <CAJ8eaTwfYvAEUXX=LMFfHvvyG1JKT4wADqofb0YdyaUtDT8GEg@mail.gmail.com>
On Fri, Jan 27, 2012 at 05:24:42AM +0000, naveen yadav wrote:
> Recently Greg decide and select linux 3.0 for long term.
>
> http://www.kroah.com/log/
> 3.0.y - this is the new "longterm" kernel release, it will be
> maintained for 2 years at the minimum by me.
>
> PS. Catalin+ Greg
> So I have one request from Mr. Catalin and Greg.
>
> Is ARM-15 support will be added in this or not. ?
It depends on how much Cortex-A15 support you mean. UP with classic MMU
is already supported as it's an ARMv7 processor. SMP with classic MMU
got merged in 3.1-rc1 (commit 7665d9d2df - "ARM: proc: add proc info for
Cortex-A15MP using classic page tables"). ARM LPAE was merged in 3.3-rc1
and generic timers probably during the next merging window.
ARM LPAE and generic timers are unlikely to be back-ported to 3.0
(though I have some patches around but they need considerable amount of
timer for maintaining in a long-term release).
--
Catalin
next prev parent reply other threads:[~2012-01-27 11:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 5:24 Long term stable kernel seletion (3.0) naveen yadav
2012-01-27 11:24 ` Catalin Marinas [this message]
2012-01-27 13:17 ` naveen yadav
2012-01-27 14:25 ` Catalin Marinas
2012-01-27 14:56 ` Greg KH
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=20120127112434.GA7757@arm.com \
--to=catalin.marinas@arm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=yad.naveen@gmail.com \
/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