From: David Miller <davem@davemloft.net>
To: linus.luessing@c0d3.blue
Cc: openwrt-devel@lists.openwrt.org, netdev@vger.kernel.org,
bridge@lists.linux-foundation.org, gregkh@linuxfoundation.org,
shemming@brocade.com
Subject: Re: Multicast packets being lost (3.10 stable)
Date: Sat, 13 Dec 2014 15:37:41 -0500 (EST) [thread overview]
Message-ID: <20141213.153741.1636406298389279104.davem@davemloft.net> (raw)
In-Reply-To: <20141210191633.GA2473@odroid>
From: Linus Lüssing <linus.luessing@c0d3.blue>
Date: Wed, 10 Dec 2014 20:16:33 +0100
> did you have a chance to look into backporting these fixes for
> stable yet?
I am not submitting -stable fixes back to 3.10 any longer, at most
I am doing 4 -stable releases and right now that is 3.18, 3.17,
v3.14, and v3.12
next prev parent reply other threads:[~2014-12-13 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 16:41 Multicast packets being lost (3.10 stable) Stephen Hemminger
2014-03-25 13:06 ` Linus Lüssing
2014-09-10 13:33 ` Linus Lüssing
2014-12-10 19:16 ` Linus Lüssing
2014-12-13 20:37 ` David Miller [this message]
2014-12-15 8:04 ` Simon Horman
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=20141213.153741.1636406298389279104.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.luessing@c0d3.blue \
--cc=netdev@vger.kernel.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=shemming@brocade.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).