linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Murali Karicheri <m-karicheri2@ti.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: <davem@davemloft.net>, <kuba@kernel.org>,
	<grygorii.strashko@ti.com>, <nsekhar@ti.com>,
	<linux-omap@vger.kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [net v2 PATCH 2/2] net: ethernet: ti: cpsw_new: fix clean up of vlan mc entries for host port
Date: Mon, 24 Aug 2020 07:09:57 -0400	[thread overview]
Message-ID: <cca548db-7da2-7aa4-660c-bc3d22d3e023@ti.com> (raw)
In-Reply-To: <20200821130002.00002367@intel.com>



On 8/21/20 4:00 PM, Jesse Brandeburg wrote:
> Murali Karicheri wrote:
> 
>> To flush the vid + mc entries from ALE, which is required when a VLAN
>> interface is removed, driver needs to call cpsw_ale_flush_multicast()
>> with ALE_PORT_HOST for port mask as these entries are added only for
>> host port. Without this, these entries remain in the ALE table even
>> after removing the VLAN interface. cpsw_ale_flush_multicast() calls
>> cpsw_ale_flush_mcast which expects a port mask to do the job.
>>
>> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
> 
> Patch looks good but please resend with a Fixes: tag.
> 
Sure will do
-- 
Murali Karicheri
Texas Instruments

  reply	other threads:[~2020-08-24 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 13:49 [net v2 PATCH 1/2] net: ethernet: ti: cpsw: fix clean up of vlan mc entries for host port Murali Karicheri
2020-08-21 13:49 ` [net v2 PATCH 2/2] net: ethernet: ti: cpsw_new: " Murali Karicheri
2020-08-21 20:00   ` Jesse Brandeburg
2020-08-24 11:09     ` Murali Karicheri [this message]
2020-08-21 19:59 ` [net v2 PATCH 1/2] net: ethernet: ti: cpsw: " Jesse Brandeburg

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=cca548db-7da2-7aa4-660c-bc3d22d3e023@ti.com \
    --to=m-karicheri2@ti.com \
    --cc=davem@davemloft.net \
    --cc=grygorii.strashko@ti.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nsekhar@ti.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).