From: Christian Dietrich <qy03fugy@stud.informatik.uni-erlangen.de>
To: Peppe CAVALLARO <peppe.cavallaro@st.com>
Cc: Christian Dietrich <qy03fugy@stud.informatik.uni-erlangen.de>,
"David S. Miller" <davem@davemloft.net>,
"netdev\@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vamos-dev\@i4.informatik.uni-erlangen.de"
<vamos-dev@i4.informatik.uni-erlangen.de>
Subject: Re: Dead Config Option STMMAC_ETH?
Date: Mon, 23 Aug 2010 10:42:26 +0200 [thread overview]
Message-ID: <86bp8tu3d9.fsf@peer.zerties.org> (raw)
In-Reply-To: <107012446AC13D4C90B85672EAF5FB0E9E0FB3CC9C@SAFEX1MAIL3.st.com> (Peppe CAVALLARO's message of "Mon, 23 Aug 2010 09:13:38 +0200")
Peppe CAVALLARO <peppe.cavallaro@st.com> writes:
[...]
> There is effort on this driver: currently the driver fully works on
> STM platforms and starts working on ARM (SPEAr Kernels). The driver
> Kconfig actually depends on the CPU_SUBTYPE_ST40 but it built on x86
> if remove this dependency (just verified). In the past, I added this
> dependency because the driver was initially tested on ST kernels
> (where we continue to have the CPU_SUBTYPE_ST40) but I can review it
> if you like.
Hm, i think it would be good if this dependency is removed, if it isn't
needed, because then a allyes config would compile test this peace of
code, and it can't die silently with changes around it.
greetz didi
--
(λ 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 prev parent reply other threads:[~2010-08-23 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 12:28 Dead Config Option STMMAC_ETH? Christian Dietrich
2010-08-23 7:13 ` Peppe CAVALLARO
2010-08-23 8:42 ` Christian Dietrich [this message]
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=86bp8tu3d9.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