linux-kernel - RE: [uclinux-dist-devel] blackfin: how is the I-pipe code supposed to be built?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1339443890.30984.96.camel@x61.thuisdomein>
Date:	Mon, 11 Jun 2012 21:44:50 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	"Zhang, Sonic" <Sonic.Zhang@...log.com>
Cc:	Mike Frysinger <vapier@...too.org>,
	"uclinux-dist-devel@...ckfin.uclinux.org" 
	<uclinux-dist-devel@...ckfin.uclinux.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"philippe.gerum@...omai.org" <philippe.gerum@...omai.org>
Subject: RE: [uclinux-dist-devel] blackfin: how is the I-pipe code supposed
 to	be built?

Sonic,

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?  


Paul Bolle

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/