From: Ben Hutchings <ben@decadent.org.uk>
To: Victor Miasnikov <vvm@tut.by>
Cc: Richard Genoud <richard.genoud@gmail.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"Patrick J. Volkerding" <volkerdi@slackware.com>,
KY Srinivasan <kys@microsoft.com>,
Mike Sterling <Mike.Sterling@microsoft.com>,
Olaf Hering <ohering@suse.de>,
davem@davemloft.net, netdev@vger.kernel.org, olaf@aepfle.de,
jasowang@redhat.com, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, stable@vger.kernel.org
Subject: Re: Kernel v3.2 used in SlackWare 14.00 please, backport all needed patches Re: [PATCH net, 1/2] hyperv: Fix a kernel warning from netvsc_linkstatus_callback()
Date: Tue, 28 May 2013 04:10:46 +0100 [thread overview]
Message-ID: <1369710646.3469.424.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <00D0FAD3528A443BAEA3E39861B3CFAD@local.st.by>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
On Thu, 2013-05-23 at 16:14 +0300, Victor Miasnikov wrote:
> Hi!
>
> > (the 3.2 version is different,
> > and it's instaging. (at not used by distros anyway))
>
> No: used
>
> Linux Kernel v3.2 used in:
> -- SlackWare 14.00
>
> This is actual stable version SlackWare
>
> Please, backport all(!) needed patches
[...]
> P.P.P.P.P.S.
>
> Sorry, if my msg not full "political correct"
>
> I preffered solve problem as possibily earler, what wait big problems
>
> Sorry, again . . .
Please read Documentation/stable_kernel_rules.txt. In short, you need
to identify the commit hash for each of the changes you want, and
provide the backported patch for any commits that can't simply be
cherry-picked. I'm not going to read through all of what you wrote to
work out exactly what's needed.
I think Slackware might do better to backport the Hyper-V drivers from
Linux 3.4, as Debian and Ubuntu have done with 3.2-based kernels. But
that sort of large backport isn't allowed on kernel.org stable branches.
Ben.
--
Ben Hutchings
If at first you don't succeed, you're doing about average.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-05-28 3:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 21:44 [PATCH net,1/2] " Haiyang Zhang
2013-04-05 21:44 ` [PATCH net,2/2] hyperv: Fix RNDIS send_completion code path Haiyang Zhang
2013-04-08 16:16 ` David Miller
2013-04-08 16:16 ` [PATCH net,1/2] hyperv: Fix a kernel warning from netvsc_linkstatus_callback() David Miller
2013-05-23 8:44 ` [PATCH net, 1/2] " Richard Genoud
2013-05-23 13:14 ` Kernel v3.2 used in SlackWare 14.00 please, backport all needed patches " Victor Miasnikov
2013-05-28 3:10 ` Ben Hutchings [this message]
2013-05-30 9:44 ` ToDo: backport to v3.2 patches Fw: use hv_storvsc instead of ata_piix for IDE disks ( but not for the CD-ROM) Re: Kernel v3.2 used in SlackWare 14.00 please, backport all needed patches Victor Miasnikov
2013-05-23 14:51 ` [PATCH net, 1/2] hyperv: Fix a kernel warning from netvsc_linkstatus_callback() Haiyang Zhang
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=1369710646.3469.424.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=Mike.Sterling@microsoft.com \
--cc=davem@davemloft.net \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ohering@suse.de \
--cc=olaf@aepfle.de \
--cc=richard.genoud@gmail.com \
--cc=stable@vger.kernel.org \
--cc=volkerdi@slackware.com \
--cc=vvm@tut.by \
/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
all inboxes | Powered by JetHome®