From: Christian Dietrich <qy03fugy@stud.informatik.uni-erlangen.de>
To: uclinux-dist-devel@blackfin.uclinux.org, linux-kernel@vger.kernel.org
Cc: vamos-dev@i4.informatik.uni-erlangen.de
Subject: CONFIG_IPIPE
Date: Wed, 28 Jul 2010 16:14:54 +0200 [thread overview]
Message-ID: <86bp9rhew1.fsf@peer.zerties.org> (raw)
Hi all!
As part of the VAMOS[0] research project at the University of
Erlangen we are looking at multiple integrity errors in linux'
configuration system.
I've been running a check on the arch/blackfin sourcetree for
config Items not defined in Kconfig and found such a case. Sourcecode
blocks depending on these Items are not reachable from a vanilla
kernel.
I've seen, that there is no configuration Option for CONFIG_IPIPE in the
vanilla kernel. There are 36 cases of dead blocks within arch/blackfin
referencing CONFIG_IPIPE. So i thought, i ask, if this is a out of tree
development, which should be merged in the future, before i start
writing patches.
Regards
Christian Dietrich
[0] http://vamos1.informatik.uni-erlangen.de
--
(λ x . x x) (λ x . x x) -- See how beatiful the lambda is
No documentation is better than bad documentation
-- Das Ausdrucken dieser Mail wird urheberrechtlich verfolgt.
next reply other threads:[~2010-07-28 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 14:14 Christian Dietrich [this message]
2010-07-28 15:14 ` CONFIG_IPIPE Mike Frysinger
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=86bp9rhew1.fsf@peer.zerties.org \
--to=qy03fugy@stud.informatik.uni-erlangen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vamos-dev@i4.informatik.uni-erlangen.de \
/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