mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: kamal.mostafa@canonical.com
Cc: stable@vger.kernel.org, jmaxwell37@gmail.com, jiri@resnulli.us,
	makita.toshiaki@lab.ntt.co.jp, stephen@networkplumber.org,
	davem@davemloft.net, bridge@lists.linux-foundation.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH][v3.13.y-ckt][PATCH 0/1] bridge: notify user space after fdb update
Date: Fri, 20 May 2016 12:59:36 -0400	[thread overview]
Message-ID: <cover.1463760264.git.joseph.salisbury@canonical.com> (raw)

BugLink: http://bugs.launchpad.net/bugs/1581585

Hello,

Please consider including upstream commit c65c7a306610ee7c13669a8f5601b472c19dc6f1
in the next v3.13.y-ckt release.  It was included in the mainline tree as of 
v3.14-rc3.  It has been tested and confirmed to resolve
http://bugs.launchpad.net/bugs/1581585 .

This commit also reques commit a5642ab4744 as a prereq.  Commit  a5642ab4744 
does not apply cleanly to v3.13-y.ckt, so I performed a backport, which is
in email 1/1


Prereq:
commit a5642ab4744bc8c5a8c7ce7c6e30c01bd6bbc691
Author: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Date:   Fri Feb 7 16:48:18 2014 +0900

    bridge: Fix the way to find old local fdb entries in br_fdb_changeaddr

Real fix:
commit c65c7a306610ee7c13669a8f5601b472c19dc6f1
Author: Jon Maxwell <jmaxwell37@gmail.com>
Date:   Thu May 29 17:27:16 2014 +1000

    bridge: notify user space after fdb update

Regards,

Joe Salisbury

             reply	other threads:[~2016-05-20 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 16:59 Joseph Salisbury [this message]
2016-05-20 16:59 ` [PATCH][3.13.y-ckt][PATCH 1/1] bridge: Fix the way to find old local fdb entries in br_fdb_changeaddr Joseph Salisbury

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=cover.1463760264.git.joseph.salisbury@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=jiri@resnulli.us \
    --cc=jmaxwell37@gmail.com \
    --cc=kamal.mostafa@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=makita.toshiaki@lab.ntt.co.jp \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stephen@networkplumber.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
Powered by JetHome