From: Mitchell Tasman <tasman@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Arm support for 3.2 kernel?
Date: Wed, 18 Jan 2012 19:26:02 -0500 [thread overview]
Message-ID: <4F17631A.6010106@domain.hid> (raw)
In-Reply-To: <4F0C9C25.5080401@domain.hid>
On 01/10/2012 03:14 PM, Gilles Chanteperdrix wrote:
> On 01/10/2012 02:13 AM, Mitchell Tasman wrote (in part):
>> Hi. I saw the recent discussion regarding ARM I-pipe and 3.x, and am
>> wondering if anyone can hazard a guess as to a timetable for 3.2 support?
>
> 3.0 is on its way. 3.1 will be next because it is the first version to
> support a new I-pipe architecture, so I was hoping to be able to skip 3.2...
Thank you for your response to my question(s). I noticed that an arm
I-pipe patchset for 3.0.13 recently landed in git.
Might you consider making 3.2 the next target for arm I-pipe support
rather than 3.1? It seems that 3.1 is already being end-of-lifed, and
e.g., that the RT-Preempt community has jumped directly from 3.0 to 3.2.
Thanks again and best regards.
next prev parent reply other threads:[~2012-01-19 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 1:13 [Xenomai-help] Arm support for 3.2 kernel? Mitchell Tasman
2012-01-10 20:14 ` Gilles Chanteperdrix
2012-01-19 0:26 ` Mitchell Tasman [this message]
2012-01-19 14:53 ` babbittner
2012-01-19 16:43 ` Terry Fryar
2012-01-21 18:03 ` Josh Karch
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=4F17631A.6010106@domain.hid \
--to=tasman@domain.hid \
--cc=xenomai@xenomai.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.