All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] kernel 3.12
Date: Mon, 25 Apr 2016 17:31:03 -0400	[thread overview]
Message-ID: <20160425213103.GL11630@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20160425202341.GI1881@hermes.click-hack.org>

On Mon, Apr 25, 2016 at 10:23:41PM +0200, Gilles Chanteperdrix wrote:
> pre and post patches allow applying an I-pipe patch to a vendor
> kernel. They make it possible for the I-pipe patch to evolve with
> little changes to the pre/post patches.

Oh right.  I guess I have been lucky enough to use a kernel close enough
to upstream to not have a problem.

-- 
Len Sorensen


  reply	other threads:[~2016-04-25 21:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 12:46 [Xenomai] kernel 3.12 Ran Shalit
2016-04-18 13:45 ` Lennart Sorensen
2016-04-18 13:47   ` Ran Shalit
2016-04-18 13:54     ` Lennart Sorensen
2016-04-18 13:56       ` Ran Shalit
2016-04-18 14:28         ` Ran Shalit
2016-04-18 14:30           ` Lennart Sorensen
2016-04-24  7:21             ` Ran Shalit
2016-04-25 14:36               ` Lennart Sorensen
2016-04-25 16:38                 ` Ran Shalit
2016-04-25 17:08                   ` Lennart Sorensen
2016-04-25 19:50                   ` Gilles Chanteperdrix
2016-04-25 20:01                     ` Ran Shalit
2016-04-25 20:09                       ` Lennart Sorensen
2016-04-25 20:23                         ` Gilles Chanteperdrix
2016-04-25 21:31                           ` Lennart Sorensen [this message]
2016-04-25 21:42                             ` Gilles Chanteperdrix
2016-04-26  6:08                         ` Jan Kiszka
2016-04-26  5:48                     ` Ran Shalit

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=20160425213103.GL11630@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --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.