[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1369710646.3469.424.camel@deadeye.wl.decadent.org.uk>
Date: Tue, 28 May 2013 04:10:46 +0100
From: Ben Hutchings <ben@...adent.org.uk>
To: Victor Miasnikov <vvm@....by>
Cc: Richard Genoud <richard.genoud@...il.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"Patrick J. Volkerding" <volkerdi@...ckware.com>,
KY Srinivasan <kys@...rosoft.com>,
Mike Sterling <Mike.Sterling@...rosoft.com>,
Olaf Hering <ohering@...e.de>, davem@...emloft.net,
netdev@...r.kernel.org, olaf@...fle.de, jasowang@...hat.com,
linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
stable@...r.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()
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.
Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)
Powered by blists - more mailing lists