netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: "Amit S. Kale" <amitkale@linsyssoft.com>
Cc: "Amit S. Kale" <amitkale@netxen.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH] netxen: sparse warning and ioctl bug fixes
Date: Wed, 6 Dec 2006 08:30:36 -0800	[thread overview]
Message-ID: <20061206083036.3de22974@localhost.localdomain> (raw)
In-Reply-To: <200612062140.35176.amitkale@linsyssoft.com>

On Wed, 6 Dec 2006 21:40:34 +0530
"Amit S. Kale" <amitkale@linsyssoft.com> wrote:

> Hi Stephen,
> 
> This patch looks good. 
> 
> ioctls: NetXen chip is far more generic and will eventually show a significant 
> amount of functionality in different products. We need ioctl analysis for 
> user level tools that can tell states of registers etc. Removing ioctls all 
> together will make any analysis from userland extremely difficult.

Use (and extend) existing ethtool interface to get registers and statistics.


> 
> Does anyone have ideas on improving this ioctl interface?
> 
> Thanks.
> -Amit
> 

  reply	other threads:[~2006-12-06 16:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05 20:07 [PATCH] netxen: sparse warning and ioctl bug fixes Stephen Hemminger
2006-12-06 16:10 ` Amit S. Kale
2006-12-06 16:30   ` Stephen Hemminger [this message]
2006-12-07 10:00 ` Jeff Garzik
2006-12-07 10:09 ` Christoph Hellwig
2006-12-15 15:57   ` [PATCH] netxen: remove private ioctl Stephen Hemminger
2006-12-15 16:04     ` Christoph Hellwig
2006-12-27  5:36     ` Amit S. Kale

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=20061206083036.3de22974@localhost.localdomain \
    --to=shemminger@osdl.org \
    --cc=amitkale@linsyssoft.com \
    --cc=amitkale@netxen.com \
    --cc=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.org \
    /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).