All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.r.fastabend@intel.com>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: netdev@vger.kernel.org, Gregory Rose <gregory.v.rose@intel.com>
Subject: Re: [PATCH v2 net-next 2/4] ixgbe: Remove driver specific fdb handlers.
Date: Fri, 01 Mar 2013 14:22:36 -0800	[thread overview]
Message-ID: <51312A2C.5030509@intel.com> (raw)
In-Reply-To: <1362151906-20993-3-git-send-email-vyasevic@redhat.com>

On 3/1/2013 7:31 AM, Vlad Yasevich wrote:
> Remove driver specific fdb handlers since they are the same
> as the default ones.
>
> CC: John Fastabend <john.r.fastabend@intel.com>
> CC: Gregory Rose <gregory.v.rose@intel.com>
> Signed-off-by: Vlad Yasevich <vyasevic@redhat.com>
> ---
>   drivers/net/ethernet/intel/ixgbe/ixgbe_main.c |   42 +------------------------
>   1 files changed, 1 insertions(+), 41 deletions(-)
                                       ^^^^^^^^^^^^^^^^
nice.

Acked-By: John Fastabend <john.r.fastabend@intel.com>

  reply	other threads:[~2013-03-01 22:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-01 15:31 [PATCH v2 net-next 0/4] Provide default fdb operation to allow mac filter setting Vlad Yasevich
2013-03-01 15:31 ` [PATCH v2 net-next 1/4] net: generic fdb support for drivers without ndo_fdb_<op> Vlad Yasevich
2013-03-01 22:20   ` John Fastabend
2013-03-01 15:31 ` [PATCH v2 net-next 2/4] ixgbe: Remove driver specific fdb handlers Vlad Yasevich
2013-03-01 22:22   ` John Fastabend [this message]
2013-03-01 15:31 ` [PATCH v2 net-next 3/4] mlx4: " Vlad Yasevich
2013-03-01 15:31 ` [PATCH v2 net-next 4/4] qlcnic: Use generic fdb handler when driver options are not enabled Vlad Yasevich
2013-03-01 21:26 ` [PATCH v2 net-next 0/4] Provide default fdb operation to allow mac filter setting David Miller
2013-03-06 20:37   ` Or Gerlitz

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=51312A2C.5030509@intel.com \
    --to=john.r.fastabend@intel.com \
    --cc=gregory.v.rose@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=vyasevic@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.