From: Mike Frysinger <vapier@gentoo.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: "Zhang, Sonic" <Sonic.Zhang@analog.com>,
"uclinux-dist-devel@blackfin.uclinux.org"
<uclinux-dist-devel@blackfin.uclinux.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"philippe.gerum@xenomai.org" <philippe.gerum@xenomai.org>
Subject: Re: [uclinux-dist-devel] blackfin: how is the I-pipe code supposed to be built?
Date: Mon, 11 Jun 2012 21:31:12 -0400 [thread overview]
Message-ID: <201206112131.14430.vapier@gentoo.org> (raw)
In-Reply-To: <1339443890.30984.96.camel@x61.thuisdomein>
[-- Attachment #1: Type: Text/Plain, Size: 787 bytes --]
On Monday 11 June 2012 15:44:50 Paul Bolle wrote:
> On Sun, 2012-06-10 at 23:05 -0400, Zhang, Sonic wrote:
> > The IPIPE patch is part of the ADEOS real time kernel patch. The
> > common part of this patch hasn't been merged into mainline by the
> > maintainer Philippe Gerum, although the Blackfin architecture part
> > was. The relative Kbuild support and Kconfig symbols are defined in
> > the ADOES common patch.
>
> What's the point of having code in the mainline tree, for over three
> years, without any Kbuild or Kconfig support?
because the Blackfin team cares about keeping ADEOS active throughout the
rewrites/updates of core code. it isn't hurting keeping the code in the
arch/blackfin/ tree, and we're ok with any overhead it implies for the team.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-06-12 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 21:50 blackfin: how is the I-pipe code supposed to be built? Paul Bolle
2012-06-11 3:05 ` [uclinux-dist-devel] " Zhang, Sonic
2012-06-11 19:44 ` Paul Bolle
2012-06-12 1:31 ` Mike Frysinger [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=201206112131.14430.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=Sonic.Zhang@analog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=philippe.gerum@xenomai.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox