netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: amirv@mellanox.com
Cc: netdev@vger.kernel.org, yevgenyp@mellanox.com, ogerlitz@mellanox.com
Subject: Re: [PATCH net-next 0/4] Mellanox driver update Jul-22-2014
Date: Tue, 22 Jul 2014 19:54:14 -0700 (PDT)	[thread overview]
Message-ID: <20140722.195414.658758946125876535.davem@davemloft.net> (raw)
In-Reply-To: <1406033052-16550-1-git-send-email-amirv@mellanox.com>

From: Amir Vadai <amirv@mellanox.com>
Date: Tue, 22 Jul 2014 15:44:08 +0300

> This patchset contains a fix by Eyal to fix a bug in mlx4_en with bonding
> alb/tlb mode.
> The second patch, by me, is an ethtool private flag that enable turning off the
> BlueFlame hardware feature.
> The last two patches, introduce a new low memory profile for mlx4_en and
> mlx4_core. This mode is useful when running from a limited resources
> environment, like kdump. This will reduce the memory consumed by both drivers
> from more than 100M to ~30M.
> 
> This patchset was applied and tested on commit 575a193 ("net: mvpp2: Fix error
> return code in mvpp2_probe")

Series applied, thanks.

      parent reply	other threads:[~2014-07-23  2:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 12:44 [PATCH net-next 0/4] Mellanox driver update Jul-22-2014 Amir Vadai
2014-07-22 12:44 ` [PATCH net-next 1/4] net/mlx4_en: current_mac isn't updated in port up Amir Vadai
2014-07-22 12:44 ` [PATCH net-next 2/4] net/mlx4_en: Disable blueflame using ethtool private flags Amir Vadai
2014-07-22 12:44 ` [PATCH net-next 3/4] net/mlx4_core: Use low memory profile on kdump kernel Amir Vadai
2014-07-22 12:44 ` [PATCH net-next 4/4] net/mlx4_en: Reduce memory consumption " Amir Vadai
2014-07-23  2:54 ` David Miller [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=20140722.195414.658758946125876535.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=amirv@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=yevgenyp@mellanox.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).