From: Greg KH <gregkh@linuxfoundation.org>
To: Smart Weblications GmbH - Florian Wiessner
<f.wiessner@smart-weblications.de>
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 06:57:45 -0700 [thread overview]
Message-ID: <20130522135745.GA14640@kroah.com> (raw)
In-Reply-To: <519CADA9.9060909@smart-weblications.de>
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>
next prev parent reply other threads:[~2013-05-22 13:57 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 ` Greg KH [this message]
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 ` 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=20130522135745.GA14640@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=f.wiessner@smart-weblications.de \
--cc=fubar@us.ibm.com \
--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