From: David Miller <davem@davemloft.net>
To: cjren@qca.qualcomm.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
qca-linux-team@qualcomm.com, nic-devel@qualcomm.com,
xiong@qca.qualcomm.com, rodrigue@qca.qualcomm.com
Subject: Re: [PATCH v2] net: add new QCA alx ethernet driver
Date: Wed, 22 Aug 2012 22:57:00 -0700 (PDT) [thread overview]
Message-ID: <20120822.225700.714020017287504609.davem@davemloft.net> (raw)
In-Reply-To: <1345480949-14800-1-git-send-email-cjren@qca.qualcomm.com>
From: <cjren@qca.qualcomm.com>
Date: Tue, 21 Aug 2012 00:42:29 +0800
> +config ALX_DEBUGFS
> + bool "Qualcomm Atheros debugging interface"
> + depends on ALX && DEBUG_FS
> + ---help---
> + This option adds ability to debug and test L1F. It can
> + support Qualcomm Atheros tools, including diagnostic, memcfg
> + and SWOI.
Sorry, no vendor specific interfaces, you have to remove this.
Anything diagnostic you think is special and unique to your piece of
hardware, is almost certainly not, and therefore needs to exist as a
generic ethtool or similar interface that other drivers can plug into,
not just your's.
Driver specific interfaces suck for several reasons, not least of
which is the fact that it leads to a terrible user experience. The
same task must be done in different ways depending upon what piece of
networking hardware and device driver are being used, which the user
should never need to know.
This is why we require that portable, sane, interfaces are added
to ethtool for driver diagnostics. That way users can perform
a task in the same way regardless of what hardware and driver
are underneath.
next prev parent reply other threads:[~2012-08-23 5:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 16:42 [PATCH v2] net: add new QCA alx ethernet driver cjren
2012-08-23 5:57 ` David Miller [this message]
2012-08-23 6:35 ` Huang, Xiong
2012-08-23 6:40 ` David Miller
2012-08-23 6:56 ` Huang, Xiong
2012-08-23 7:13 ` David Miller
2012-08-23 10:28 ` Luis R. Rodriguez
2012-08-23 21:09 ` Ben Hutchings
2012-08-24 1:55 ` Huang, Xiong
2012-08-24 2:09 ` Ben Hutchings
2012-08-24 2:39 ` Huang, Xiong
2012-08-24 4:32 ` Luis R. Rodriguez
2012-08-24 5:34 ` Luis R. Rodriguez
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=20120822.225700.714020017287504609.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cjren@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic-devel@qualcomm.com \
--cc=qca-linux-team@qualcomm.com \
--cc=rodrigue@qca.qualcomm.com \
--cc=xiong@qca.qualcomm.com \
/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).