All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Debian package of Xenomai 2.6.4
Date: Fri, 26 Jun 2015 15:47:02 +0200	[thread overview]
Message-ID: <71780767.LPXQKYItBR@soho> (raw)
In-Reply-To: <20150626124947.GD23673@hermes.click-hack.org>

El Divendres, 26 de juny de 2015, a les 14:49:47, Gilles Chanteperdrix va 
escriure:
> On Thu, Jun 25, 2015 at 11:10:32PM +0200, Leopold Palomo-Avellaneda wrote:
> > El Dijous, 25 de juny de 2015, a les 22:56:08, Gilles Chanteperdrix va
> > 
> > escriure:
> > > On Thu, Jun 25, 2015 at 01:43:51PM +0200, Leopold Palomo-Avellaneda 
wrote:
> > > > - I have removed the previous debian patches (incorporated by
> > > > upstream)
> > > > but I have added one commit from upstream to build with 2.6.4 kernels
> > > > =>
> > > > 3.11.
> > > 
> > > Would be interested to know about this patch, because Xenomai 2.6.4
> > > has been built-tested with kernels up to 3.14, so, there is no
> > > problem to build it with versions superior to 3.11 that I know of.
> > 
> > Gilles,
> > 
> > on 2014-09-25 you released 2.6.4.
> > 
> > on 2015-01-16 you did a commit (can/flexcan: fixup for kernel release >=
> > 3.11) that is the one that I noticed.
> 
> Indeed, merging that one makes sense.
> 
> > However, looking now the log there are two commits that will affect on arm
> > platforms:
> > 2014-11-24	hal/arm: fixup for Linux 3.16
> > 2014-11-05	hal: fixups for kernel 3.16
> > 
> > So, probably I will need them too.
> 
> I would not recommend that. Xenomai 2.6.4 
ftp://ftp.kernel.org/pub/linux/kernel/v3.x/linux-3.16.7.tar.xzhas been tested 
and
> released to support kernel versions up to 3.14, so, I would keep it
> like that. Xenomai 3.0 supports higher kernel versions, Xenomai
> 2.6.5 will probably also, but I will test the 3.16 and 3.18 versions
> extensively before releasing it.

Perfect. I have _only_ tested amd64 platform and it have been worked with 3.16 
without any noticeable problem.

Leopold 

-- 
--
Linux User 152692     GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150626/ada46503/attachment.sig>

      reply	other threads:[~2015-06-26 13:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 11:43 [Xenomai] Debian package of Xenomai 2.6.4 Leopold Palomo-Avellaneda
2015-06-25 12:01 ` Gilles Chanteperdrix
2015-06-25 12:41   ` Leopold Palomo-Avellaneda
2015-06-25 12:54     ` Gilles Chanteperdrix
2015-06-25 13:56       ` Leopold Palomo-Avellaneda
2015-06-25 14:06         ` Gilles Chanteperdrix
2015-06-25 15:35           ` Leopold Palomo-Avellaneda
2015-06-25 20:56 ` Gilles Chanteperdrix
2015-06-25 21:10   ` Leopold Palomo-Avellaneda
2015-06-26 12:44     ` Gilles Chanteperdrix
2015-06-26 12:49     ` Gilles Chanteperdrix
2015-06-26 13:47       ` Leopold Palomo-Avellaneda [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=71780767.LPXQKYItBR@soho \
    --to=leo@alaxarxa.net \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.