From: Jay Vosburgh <fubar@us.ibm.com>
To: f.wiessner@smart-weblications.de
Cc: Greg KH <gregkh@linuxfoundation.org>,
davem@davemloft.net, liquidhorse@gmail.com, andy@greyhouse.net,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, nikolay@redhat.com, vfalico@redhat.com
Subject: Re: https://lkml.org/lkml/2013/2/1/531
Date: Wed, 22 May 2013 14:54:57 -0700 [thread overview]
Message-ID: <2972.1369259697@death.nxdomain> (raw)
In-Reply-To: <519D37F4.2030202@smart-weblications.de>
Smart Weblications GmbH - Florian Wiessner wrote:
>Am 22.05.2013 22:04, schrieb Greg KH:
>
>
>>>
>>> https://kernel.googlesource.com/pub/scm/linux/kernel/git/jkirsher/net-next/+/567b871e503316b0927e54a3d7c86d50b722d955%5E!/
>>
>> Ok, that's what we need.
>>
>> Now, please cc: the developers / maintainers of that patch and ask them
>> to have it included in the 3.4-stable kernel series.
>>
>> Then, if they agree, the network maintainer will pick it up and send it
>> to me for inclusion.
>>
>
>i set committer David S. Miller <davem@davemloft.net> in cc already, but do not
>know the network maintainer...
>
>this seems to me that "Matthew O'Connor" <liquidhorse@gmail.com> sent this to
>netdev on 2013-02-01:
>
>http://lists.openwall.net/netdev/2013/02/01/86
>
>but i couldn't find a trace of the patch in 3.4.36?!
The patch in question here is in net-next; the commit is:
commit 567b871e503316b0927e54a3d7c86d50b722d955
Author: zheng.li <zheng.x.li@oracle.com>
Date: Tue Nov 27 23:57:04 2012 +0000
bonding: rlb mode of bond should not alter ARP originating via bridge
The additional change in the backport from Matthew O'Connor (to
add ether_addr_equal_64bits) appears to still be necessary for 3.4.46.
Alternatively, the patch could utilize ether_addr_equal instead, to
minimize the change set. Greg, do you have a preference there?
Submissions for stable from networking normally go through
Davem; I can check the patch and repost it to netdev against 3.4.46 if
everybody is ok with that.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next prev parent reply other threads:[~2013-05-22 21:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 11:36 https://lkml.org/lkml/2013/2/1/531 Smart Weblications GmbH - Florian Wiessner
2013-05-22 13:57 ` https://lkml.org/lkml/2013/2/1/531 Greg KH
2013-05-22 16:16 ` https://lkml.org/lkml/2013/2/1/531 Smart Weblications GmbH - Florian Wiessner
2013-05-22 16:23 ` https://lkml.org/lkml/2013/2/1/531 Greg KH
2013-05-22 18:16 ` https://lkml.org/lkml/2013/2/1/531 Smart Weblications GmbH - Florian Wiessner
2013-05-22 19:06 ` https://lkml.org/lkml/2013/2/1/531 Greg KH
2013-05-22 19:35 ` https://lkml.org/lkml/2013/2/1/531 Smart Weblications GmbH - Florian Wiessner
2013-05-22 20:04 ` https://lkml.org/lkml/2013/2/1/531 Greg KH
2013-05-22 21:26 ` https://lkml.org/lkml/2013/2/1/531 Smart Weblications GmbH - Florian Wiessner
2013-05-22 21:54 ` Jay Vosburgh [this message]
2013-05-22 22:24 ` https://lkml.org/lkml/2013/2/1/531 Smart Weblications GmbH - Florian Wiessner
2013-05-22 22:32 ` https://lkml.org/lkml/2013/2/1/531 Greg KH
2013-05-22 23:17 ` https://lkml.org/lkml/2013/2/1/531 Matthew O'Connor
2013-05-23 10:24 ` https://lkml.org/lkml/2013/2/1/531 Smart Weblications GmbH - Florian Wiessner
2013-05-23 12:35 ` https://lkml.org/lkml/2013/2/1/531 Matthew O'Connor
2013-05-23 13:36 ` https://lkml.org/lkml/2013/2/1/531 Smart Weblications GmbH - Florian Wiessner
2013-05-23 12:46 ` https://lkml.org/lkml/2013/2/1/531 Matthew O'Connor
2013-05-29 1:01 ` https://lkml.org/lkml/2013/2/1/531 Smart Weblications GmbH - Florian Wiessner
2013-05-29 1:10 ` https://lkml.org/lkml/2013/2/1/531 David Miller
2013-05-29 1:15 ` https://lkml.org/lkml/2013/2/1/531 Greg KH
2013-06-13 1:15 ` https://lkml.org/lkml/2013/2/1/531 Ben Hutchings
2013-06-18 11:47 ` https://lkml.org/lkml/2013/2/1/531 Smart Weblications GmbH - Florian Wiessner
2013-06-18 17:23 ` https://lkml.org/lkml/2013/2/1/531 Matthew O'Connor
2013-06-20 15:59 ` https://lkml.org/lkml/2013/2/1/531 Smart Weblications GmbH - Florian Wiessner
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=2972.1369259697@death.nxdomain \
--to=fubar@us.ibm.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=f.wiessner@smart-weblications.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liquidhorse@gmail.com \
--cc=nikolay@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vfalico@redhat.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).