All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Wayne Warren <wwarren@emacinc.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Adeos I-Pipe patch problem on vendor-specific kernel
Date: Tue, 02 Oct 2012 23:32:27 +0200	[thread overview]
Message-ID: <506B5D6B.80005@xenomai.org> (raw)
In-Reply-To: <1349212116.21898.108.camel@ENG-09-LX.emacinc.com>

On 10/02/2012 11:08 PM, Wayne Warren wrote:

> Howdy folks,


Hi

(snip)
> The tag that I have my eye on is ipip-2.6.37.6-arm-1.18-03 which I

> believe would correspond with the .patch file listed above. In fact, I
> have applied this patch and again resolved the merge conflicts, but run
> into a problem in that the Makefile/Kconfig kernel configuration
> variables do not seem to be included in that code. What seems to happen
> instead in the prepare-kernel.sh script adds them when patching the
> kernel. It seems like this script may do other important tasks as well.
> 
> I am hoping someone can advise me with regard to either how to proceed
> without those variables or maybe offer advice for generally how to
> proceed with this attempt to pull in the i-pipe patches for a
> vendor-specific kernel branch.


You need to run prepare-kernel.sh with the I-pipe tree as well.
prepare-kernel.sh will simply skip the step where it tries to apply the
adeos patch. Actually, that is the way we maintain the Xenomai and the
I-pipe patch: we work with git and compile the prepared kernel.

To merge the I-pipe tree with a vendor tree, you can use git merge.


-- 
                                                                Gilles.


  reply	other threads:[~2012-10-02 21:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 21:08 [Xenomai] Adeos I-Pipe patch problem on vendor-specific kernel Wayne Warren
2012-10-02 21:32 ` Gilles Chanteperdrix [this message]
2012-10-02 21:35   ` Gilles Chanteperdrix
2012-10-04 16:57     ` Wayne Warren
2012-10-04 17:09       ` Gilles Chanteperdrix
2012-10-04 18:02         ` Gilles Chanteperdrix
2012-10-05  8:06         ` Gilles Chanteperdrix
2012-10-05 18:47           ` Wayne Warren
2012-10-05 20:16             ` Gilles Chanteperdrix
2012-10-05 21:47               ` Wayne Warren
2012-10-05 22:43                 ` Gilles Chanteperdrix
2012-10-06  4:29                   ` Wayne Warren
2012-10-06  9:46                     ` Gilles Chanteperdrix
2012-10-09 20:55                       ` Wayne Warren
2012-10-09 21:12                         ` Gilles Chanteperdrix
2012-10-19 21:22                           ` Wayne Warren
2012-10-20  1:33                             ` Gilles Chanteperdrix
2012-10-22 19:22                               ` Wayne Warren
2012-10-22 19:25                                 ` Gilles Chanteperdrix
2012-10-22 19:34                                   ` Wayne Warren
2012-10-22 21:12                                     ` Gilles Chanteperdrix
2012-10-23 15:32                                       ` Wayne Warren
2012-10-23 20:12                                         ` Gilles Chanteperdrix
2012-10-24 17:32                                           ` Wayne Warren
2012-10-24 17:38                                             ` Gilles Chanteperdrix
2012-10-24 17:55                                               ` Wayne Warren
2012-10-24 18:05                                                 ` Gilles Chanteperdrix
2012-10-24 18:26                                                   ` Wayne Warren
2012-10-24 18:36                                                     ` Gilles Chanteperdrix
2012-10-24 17:36                                           ` Wayne Warren
2012-10-24 17:57                                             ` Gilles Chanteperdrix
2012-10-20  8:24                             ` Gilles Chanteperdrix
2012-10-19 21:32                           ` Wayne Warren
2012-10-20  1:36                             ` Gilles Chanteperdrix

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=506B5D6B.80005@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=wwarren@emacinc.com \
    --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.