netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Debashis Dutt <debdut@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: shemminger@vyatta.com, rmody@brocade.com, netdev@vger.kernel.org,
	huangj@brocade.com, amathur@brocade.com, ddutt@brocade.com
Subject: Re: [RFC PATCH 1/1] bna: Generic Netlink Interface to collect FW trace
Date: Thu, 28 Apr 2011 10:51:27 -0700	[thread overview]
Message-ID: <BANLkTimOuF+HtLxsmTGVpC7ahU_NFy_L2g@mail.gmail.com> (raw)
In-Reply-To: <20110426.191707.71110914.davem@davemloft.net>

On Tue, Apr 26, 2011 at 7:17 PM, David Miller <davem@davemloft.net> wrote:
> From: Debashis Dutt <debdut@gmail.com>
> Date: Tue, 26 Apr 2011 19:16:29 -0700
>
>> However, since the generic netlink is a more generic interface, we could use
>> this infrastructure in the driver for commands which are not part of
>> other standard tools.
>
> You aren't the only device in the world that might want to provide
> a facility to fetch firmware traces.
>
> This isn't really a niche thing specific to your device at all.
>

David,

Agreed.

In that case should we use debugfs for collecting f/w trace,
but use generic netlink for other h/w specific commands?

 Thanks
 --Debashis

  reply	other threads:[~2011-04-28 17:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  1:51 [RFC PATCH 1/1] bna: Generic Netlink Interface to collect FW trace Rasesh Mody
2011-04-27  1:59 ` Stephen Hemminger
2011-04-27  2:16   ` Debashis Dutt
2011-04-27  2:17     ` David Miller
2011-04-28 17:51       ` Debashis Dutt [this message]
2011-04-28 19:19         ` David Miller

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=BANLkTimOuF+HtLxsmTGVpC7ahU_NFy_L2g@mail.gmail.com \
    --to=debdut@gmail.com \
    --cc=amathur@brocade.com \
    --cc=davem@davemloft.net \
    --cc=ddutt@brocade.com \
    --cc=huangj@brocade.com \
    --cc=netdev@vger.kernel.org \
    --cc=rmody@brocade.com \
    --cc=shemminger@vyatta.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).