From: Smart Weblications GmbH - Florian Wiessner <f.wiessner@smart-weblications.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: davem@davemloft.net, liquidhorse@gmail.com, andy@greyhouse.net,
fubar@us.ibm.com, 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 21:35:11 +0200 [thread overview]
Message-ID: <519D1DEF.8090206@smart-weblications.de> (raw)
In-Reply-To: <20130522190640.GA20276@kroah.com>
Hi Greg,
Am 22.05.2013 21:06, schrieb Greg KH:> On Wed, May 22, 2013 at 08:16:25PM +0200,
Smart Weblications GmbH - Florian Wiessner wrote:
>> Hi,
>>
>>
>> Am 22.05.2013 18:23, schrieb Greg KH:
>>> On Wed, May 22, 2013 at 06:16:11PM +0200, Smart Weblications GmbH - Florian
Wiessner wrote:
>>>> Am 22.05.2013 15:57, schrieb Greg KH:
>>>>> On Wed, May 22, 2013 at 01:36:09PM +0200, Smart Weblications GmbH -
Florian Wiessner wrote:
>>>>>> Hi,
>>>>>>
>>>>>> why is this patch still not backported to 3.4?
>>>>>>
>>>>>> I today tried 3.4.46 from kernel.org, but the patch STILL seems _NOT_
included?
>>>>>>
>>>>>> WHY IS THAT?
>>>>>
>>>>> <formletter>
>>>>>
>>>>> This is not the correct way to submit patches for inclusion in the
>>>>> stable kernel tree. Please read Documentation/stable_kernel_rules.txt
>>>>> for how to do this properly.
>>>>>
>>>>> </formletter>
>>>>>
>>>>
>>>>
>>>> I don't want to submit a patch - i wanted to know why this patch still is
not in
>>>> the kernel (it is afaics at least 6 months old!)
>>>
>>> Perhaps because it was not submitted properly as documented above?
>>>
>>
>> Well, i don't know. I have not written that patch, but tested and applied it
>> against 3.4.36 where it worked fine.
>>
>> But i am unable to apply it to 3.4.46 (there are rejects if i try to apply it,
>> obviously because there were changes in the meanwhile) - It would be cool if
>> someone could tell if that patch is really needed anymore with 3.4.46.
>>
>> I am no C coder and only have little C experience, but i'd like to use this
>> patch with current 3.4 stable Kernel or at least make sure that this patch is
>> not needed anymore with current stable kernels...
>
> Why do you think that it is needed? And does it match up to a specific
> change that is already in Linus's tree? That is a requirement here.
>
It is needed, because without it (at least in 3.4.36) virtualized guests
(kvm/qemu) are unable to use br0 (bridge) if the bridge uses a bond with mode 6
(balance-alb).
https://kernel.googlesource.com/pub/scm/linux/kernel/git/jkirsher/net-next/+/567b871e503316b0927e54a3d7c86d50b722d955%5E!/
http://lkml.indiana.edu/hypermail/linux/kernel/1302.0/00539.html
Thanks,
--
Mit freundlichen Grüßen,
Florian Wiessner
Smart Weblications GmbH
Martinsberger Str. 1
D-95119 Naila
fon.: +49 9282 9638 200
fax.: +49 9282 9638 205
24/7: +49 900 144 000 00 - 0,99 EUR/Min*
http://www.smart-weblications.de
--
Sitz der Gesellschaft: Naila
Geschäftsführer: Florian Wiessner
HRB-Nr.: HRB 3840 Amtsgericht Hof
*aus dem dt. Festnetz, ggf. abweichende Preise aus dem Mobilfunknetz
next prev parent reply other threads:[~2013-05-22 19:35 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 ` Smart Weblications GmbH - Florian Wiessner [this message]
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 ` https://lkml.org/lkml/2013/2/1/531 Jay Vosburgh
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=519D1DEF.8090206@smart-weblications.de \
--to=f.wiessner@smart-weblications.de \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--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