From: David Miller <davem@davemloft.net>
To: ogerlitz@mellanox.com
Cc: netdev@vger.kernel.org, amirv@mellanox.com, ronye@mellanox.com
Subject: Re: [PATCH net-next 0/6] net/mlx4: Add support to SRIOV VF management ndo calls
Date: Thu, 25 Apr 2013 04:33:11 -0400 (EDT) [thread overview]
Message-ID: <20130425.043311.783987350023639431.davem@davemloft.net> (raw)
In-Reply-To: <5178E535.10804@mellanox.com>
From: Or Gerlitz <ogerlitz@mellanox.com>
Date: Thu, 25 Apr 2013 11:11:33 +0300
> On 24/04/2013 23:30, David Miller wrote:
>> From: Or Gerlitz <ogerlitz@mellanox.com>
>> Date: Wed, 24 Apr 2013 19:41:08 +0300
>>
>>> This series adds support for the SRIOV ndo_set_vf callbacks to the
>>> mlx4 driver.
>>>
>>> Series done against the net-next tree as of commit 0c501345c
>>> "batman-adv: fix
>>> global protection fault during soft_iface destruction".
>>>
>>> We have successfully tested the series on net-next, except for getting
>>> the VF link info issue I have reported earlier today on netdev, we
>>> see the problem for both ixgbe and mlx4 VFs. Just to make sure get
>>> VF config is working OK with patch #6 - we have run it over 3.8.8 too.
>> Series applied, thanks.
>
> Hi Dave, Looking on your patchwork archive, I see indeed that the
> series was accepted, e.g
>
> patch 1/6 http://patchwork.ozlabs.org/patch/239279/
> patch 2/6 http://patchwork.ozlabs.org/patch/239274/
> patch 3/6 http://patchwork.ozlabs.org/patch/239277/
> patch 4/6 http://patchwork.ozlabs.org/patch/239276/
> patch 5/6 http://patchwork.ozlabs.org/patch/239278/
> patch 6/6 http://patchwork.ozlabs.org/patch/239275/
>
> but for some reason the patches don't appear on your kernel.org
> net-next tree, anything went wrong here?
Actually, the series didn't apply, I have no idea why I said that I
applied it.
It conflicts with other changes already in net-next, namely the
NETIF_F_* vlan hw capability flag renaming done by Patrick McHardy.
Also, in patch #4:
/home/davem/src/GIT/net-next/.git/rebase-apply/patch:125: new blank line at EOF.
do not add files that end in an empty line.
Please fix this all up and resubmit, thanks.
prev parent reply other threads:[~2013-04-25 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 16:41 [PATCH net-next 0/6] net/mlx4: Add support to SRIOV VF management ndo calls Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 1/6] net/mlx4: Add reference counting to MAC registeration Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 2/6] net/mlx4: Add structures to keep VF Ethernet ports information Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 3/6] net/mlx4: Add set VF mac address support Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 4/6] net/mlx4: Add set VF default vlan ID and priority support Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 5/6] net/mlx4: Add VF MAC spoof checking support Or Gerlitz
2013-04-24 16:41 ` [PATCH net-next 6/6] net/mlx4: Add support to get VF config Or Gerlitz
2013-04-24 20:30 ` [PATCH net-next 0/6] net/mlx4: Add support to SRIOV VF management ndo calls David Miller
2013-04-25 8:11 ` Or Gerlitz
2013-04-25 8:33 ` 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=20130425.043311.783987350023639431.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amirv@mellanox.com \
--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).