netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: netdev@vger.kernel.org, Rony Efraim <ronye@mellanox.com>,
	"David S. Miller" <davem@davemloft.net>,
	Or Gerlitz <ogerlitz@mellanox.com>
Subject: Re: [PATCH] net/core: Add VF link state control policy
Date: Tue, 10 Jun 2014 16:12:08 -0400	[thread overview]
Message-ID: <1402431128.9149.8.camel@firewall.xsintricity.com> (raw)
In-Reply-To: <539765F4.10506@cogentembedded.com>

[-- Attachment #1: Type: text/plain, Size: 753 bytes --]

On Wed, 2014-06-11 at 00:09 +0400, Sergei Shtylyov wrote:
> Hello.
> 
> On 06/10/2014 11:59 PM, Doug Ledford wrote:
> 
> > Commit 1d8faf48c7 added VF link state control to the netlink VF nested
> 
>     Please also specify that commit's summary line in parens.

It was almost a carbon copy of my own commit summary:

(net/core: Add VF link state control)

> 
> > structure, but failed to add a proper entry for the new structure into
> > the VF policy table.  Add the missing entry so the table and the actual
> > data copied into the netlink nested struct are in sync.
> 
> > Signed-off-by: Doug Ledford <dledford@redhat.com>
> 
> WBR, Sergei
> 


-- 
Doug Ledford <dledford@redhat.com>
              GPG KeyID: 0E572FDD



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-06-10 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 19:59 [PATCH] net/core: Add VF link state control policy Doug Ledford
2014-06-10 20:09 ` Sergei Shtylyov
2014-06-10 20:12   ` Doug Ledford [this message]
2014-06-11  3:47     ` David Miller
2014-06-11  8:01 ` Or Gerlitz
  -- strict thread matches above, loose matches on Subject: below --
2014-06-11 14:38 Doug Ledford
2014-06-11 22:59 ` 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=1402431128.9149.8.camel@firewall.xsintricity.com \
    --to=dledford@redhat.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=ronye@mellanox.com \
    --cc=sergei.shtylyov@cogentembedded.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).