Netdev List
 help / color / mirror / Atom feed
From: Christian Dietrich <qy03fugy@stud.informatik.uni-erlangen.de>
To: "David S. Miller" <davem@davemloft.net>,
	Giuseppe Cavallaro <peppe.cavallaro@st.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "vamos-dev\@i4.informatik.uni-erlangen.de"
	<vamos-dev@i4.informatik.uni-erlangen.de>
Subject: Dead Config Option STMMAC_ETH?
Date: Tue, 10 Aug 2010 14:28:47 +0200	[thread overview]
Message-ID: <86r5i6vegw.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 drivers/net/stmmac 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 -- dead code. I've seen such dead blocks made on purpose
e.g. while integrating new features into the kernel but generally
they're just useless.

As far as i can see in drivers/net/stmmac/Kconfig STMMAC_ETH and several
depending flags are dead in the linux vanilla kernel, because it depends
on CPU_SUBTYPE_ST40, but there isn't a Kconfig option for that. But
f96691872439ab2071171d4531c4a95b5d493ae5 suggests, that support for this
ST40 plattform was removed in 2007.

There seems to be, that there was much effort on the stmmac drivers in
the last few months, so i just wanted to ask if this problem is known.

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.

             reply	other threads:[~2010-08-10 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-10 12:28 Christian Dietrich [this message]
2010-08-23  7:13 ` Dead Config Option STMMAC_ETH? Peppe CAVALLARO
2010-08-23  8:42   ` Christian Dietrich
2010-08-23  8:44     ` Peppe CAVALLARO

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=86r5i6vegw.fsf@peer.zerties.org \
    --to=qy03fugy@stud.informatik.uni-erlangen.de \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --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