From: David Miller <davem@davemloft.net>
To: ogerlitz@mellanox.com
Cc: netdev@vger.kernel.org, jackm@dev.mellanox.co.il, ronye@mellanox.com
Subject: Re: [PATCH net-next 0/2] net/mlx4: Add dynamic policy changes to the SRIOV eSwitch support
Date: Mon, 01 Jul 2013 13:12:55 -0700 (PDT) [thread overview]
Message-ID: <20130701.131255.894732078933976198.davem@davemloft.net> (raw)
In-Reply-To: <1372349122-23390-1-git-send-email-ogerlitz@mellanox.com>
From: Or Gerlitz <ogerlitz@mellanox.com>
Date: Thu, 27 Jun 2013 19:05:20 +0300
> This patch set from Jack and Rony uses the UPDATE_QP new firmware command
> to allow for dynamic policy changes of PF controlled VF vlan/qos and link-state.
>
> Done against net-next commit 8599b52e14 "bonding: add an option to fail when any
> of arp_ip_target is inaccessible"
Applied, but in patch #2:
+ /* even if the UPDATE_QP command isn't supported, we still want
+ * to set this VF link according to the admin directive
+ */
Those last two lines start with a space, then TAB(s), which I had to
fix up. GIT even warns about this when I apply your patches.
next prev parent reply other threads:[~2013-07-01 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 16:05 [PATCH net-next 0/2] net/mlx4: Add dynamic policy changes to the SRIOV eSwitch support Or Gerlitz
2013-06-27 16:05 ` [PATCH net-next 1/2] net/mlx4_core: Dynamic VST to VST vlan/qos changes Or Gerlitz
2013-06-27 16:05 ` [PATCH net-next 2/2] net/mlx4_core: Add HW enforcement to VF link state Or Gerlitz
2013-07-01 20:12 ` David Miller [this message]
2013-07-02 4:40 ` [PATCH net-next 0/2] net/mlx4: Add dynamic policy changes to the SRIOV eSwitch support 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=20130701.131255.894732078933976198.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jackm@dev.mellanox.co.il \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=ronye@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).