From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>, dev@dpdk.org
Cc: Ivan Malov <ivan.malov@oktetlabs.ru>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/sfc: set multicast address list in started state only
Date: Thu, 9 Mar 2017 15:52:26 +0000 [thread overview]
Message-ID: <30dee34d-3c74-5d9e-14ad-df5ed1ef4e3e@intel.com> (raw)
In-Reply-To: <1488465648-27351-1-git-send-email-arybchenko@solarflare.com>
On 3/2/2017 2:40 PM, Andrew Rybchenko wrote:
> From: Ivan Malov <ivan.malov@oktetlabs.ru>
>
> According to 'libefx' API requirements, one is allowed to
> apply multicast address list to the port in started state
> only, otherwise the new array should be copied to a local
> storage in order to be applied during the next port start
>
> Fixes: 0fa0070e4391 ("net/sfc: support multicast addresses list controls")
> Coverity issue: 141296
>
> Fixes: e9ddf37a507d ("net/sfc: fix setting empty multicast list")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
> Reviewed-by: Andrew Lee <alee@solarflare.com>
> Reviewed-by: Andy Moreton <amoreton@solarflare.com>
Hi Andrew,
This patch does not apply clean to next-net because of other sfc patches
get first. Can you please rebase the patch to latest next-net?
Thanks,
ferruh
next prev parent reply other threads:[~2017-03-09 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 14:40 Andrew Rybchenko
2017-03-09 15:52 ` Ferruh Yigit [this message]
2017-03-09 16:21 ` [dpdk-stable] [PATCH v2] " Andrew Rybchenko
2017-03-14 15:18 ` Ferruh Yigit
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=30dee34d-3c74-5d9e-14ad-df5ed1ef4e3e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ivan.malov@oktetlabs.ru \
--cc=stable@dpdk.org \
/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).