netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Fastabend <john.r.fastabend@intel.com>
To: s-paulraj@ti.com
Cc: David Miller <davem@davemloft.net>,
	cyril@ti.com, mugunthanvnm@ti.com, netdev@vger.kernel.org
Subject: Re: [PATCH] netdev: driver: ethernet: add sysfs interface for ti cpsw
Date: Tue, 03 Jul 2012 16:38:08 -0700	[thread overview]
Message-ID: <4FF38260.2040702@intel.com> (raw)
In-Reply-To: <20120703.161623.1843927245895613219.davem@davemloft.net>

On 7/3/2012 4:16 PM, David Miller wrote:
> From: <s-paulraj@ti.com>
> Date: Tue, 3 Jul 2012 15:51:26 -0400
>
>> From: Sandeep Paulraj <s-paulraj@ti.com>
>>
>> This patch adds sysfs entries for address lookup engine entries and
>> control for the ALE(address lookup engine) found in TI SOC's.
>>
>>
>> Signed-off-by: Sandeep Paulraj <s-paulraj@ti.com>
>
> You may not create private, driver specific, unique interfaces to
> configure your hardware.
>
> You must use existing facilities such as ethtool to add such things.
> If the existing facilities are insufficient, you must extend them to
> meet your (and potentially other's) needs.
> --

I can't seem to dig up the original email perhaps my server is slow
today but did you consider using these hooks ndo_fdb_add(),
ndo_fdb_del(), and ndo_fdb_dump() added recently.

These are for adding/deleting and dumping the address forwarding
databases. Failing that would something like this RFC with another
attribute work,

http://comments.gmane.org/gmane.linux.network/232104

Thanks,
John

      reply	other threads:[~2012-07-03 23:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1341345086-25093-1-git-send-email-s-paulraj@ti.com>
2012-07-03 23:16 ` [PATCH] netdev: driver: ethernet: add sysfs interface for ti cpsw David Miller
2012-07-03 23:38   ` John Fastabend [this message]

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=4FF38260.2040702@intel.com \
    --to=john.r.fastabend@intel.com \
    --cc=cyril@ti.com \
    --cc=davem@davemloft.net \
    --cc=mugunthanvnm@ti.com \
    --cc=netdev@vger.kernel.org \
    --cc=s-paulraj@ti.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).