From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: manfred@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] twl4030-irq takes 50%cpu constantly on omap3 gumstix overo
Date: Fri, 28 Oct 2011 20:40:49 +0200 [thread overview]
Message-ID: <4EAAF731.4020409@domain.hid> (raw)
In-Reply-To: <4EAAD83D.3020503@domain.hid>
On 10/28/2011 06:28 PM, Manfred Quack wrote:
> However: is there a "clean" or "simple" way to apply the adeos-patches
> to the omap3-<>-kernels?
I do not think so. The only answer is: get the omap changes merged into
the mainline kernel, and use the mainline kernel. Because from a
maintenance point of view, maintaining one patch for each version of the
kernel is enough work to want and avoid maintaining versions for several
vendor-specific trees.
That said, if there are not many differences:
- we can arrange for the hunks to apply to both branches (we do this for
the at91 patch);
- we can provide two patches, a pre-patch applied before the adeos patch
(basically reverting all the changes causing conflicts), and a
post-patch applied after the adeos patch solving the conflicts (we did
this for instance for the imx kernel for 2.6.38)
I do not want to do this work for the omap branch, but if someone
provides the patches, we could find a way to make them available in the
tree, making it clear that it is not patches that we validated (for
instance creating a "contrib" directory). I am afraid, however, that
such patches would bitrot rapidly.
--
Gilles.
next prev parent reply other threads:[~2011-10-28 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 14:14 [Xenomai-help] twl4030-irq takes 50%cpu constantly on omap3 gumstix overo Manfred
2011-10-28 14:25 ` Gilles Chanteperdrix
[not found] ` <4EAAD83D.3020503@domain.hid>
2011-10-28 18:40 ` Gilles Chanteperdrix [this message]
2011-10-28 18:53 ` Gilles Chanteperdrix
[not found] ` <4EAEEB5B.7040907@domain.hid>
2011-11-01 17:17 ` 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=4EAAF731.4020409@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=manfred@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.