From: Christoph Egger <siccegge@stud.informatik.uni-erlangen.de>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
viro@ftp.linux.org.uk
Cc: siccegge@stud.informatik.uni-erlangen.de,
Reinhard.Tartler@informatik.uni-erlangen.de
Subject: Obsolete config in kernel (epic100) source (CONFIG_BIG_ENDIAN)
Date: Wed, 20 Jan 2010 12:50:23 +0100 [thread overview]
Message-ID: <20100120115022.GA3580@faui49.informatik.uni-erlangen.de> (raw)
Hi all!
As part of the VAMOS[0] research project at the University of
Erlangen we're checking referential integrity between kernel KConfig
options and in-code Conditional blocks.
The epic100 kernel dirver checks the variable
CONFIG_BIG_ENDIAN for turning on byteswapping. This Variable seems to
only have ever existed as a configuration option on the sh64 Platform
and is even there now renamed and no longer existent. SO I fear the
code won't behave as expected.
I'm not attaching any patch as I'm not sure how to correctly
handle Endianess.
Please keep me informed of this patch getting confirmed /
merged so we can keep track of it.
Regards
Christoph Egger
reply other threads:[~2010-01-20 11:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100120115022.GA3580@faui49.informatik.uni-erlangen.de \
--to=siccegge@stud.informatik.uni-erlangen.de \
--cc=Reinhard.Tartler@informatik.uni-erlangen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).