Hi!
B.H.> I think Slackware might do better to
B.H.> backport the Hyper-V drivers from Linux 3.4,
In SlackWare 14.1 used Linux Kernel v3.8.X
with already fixed source code
i.e. "use hv_storvsc instead of ata_piix for IDE disks ( but not for the CD-ROM)"
work as need
But, in SlackWare 14.00 ( actual stable version of SlackWare)
used Linux Kernel v3.2
( Because backport requested at 2012-06-08 ( and apply to v3.4 -- Thanks!) has been ignored ( linux-3.2.45.tar.xz has
non-fixed ata_piix.c) in part v3.2
I ask about backport on 08/16/2012 09:53 AM :
----- Original Message -----
From: "Patrick J. Volkerding"
To: "Victor Miasnikov" vvm
Sent: Thursday, August 16, 2012 7:00 PM
Subject: Re: b3) Please: backport to Slackware 14.0 patches 1b) db63a4c8115a libata 1) cd006086fa5d ata_piix Fw:
Slackware 14.0 RC2 in virtual computer ( guest ) on Hyper-V
On 08/16/2012 09:53 AM, Victor Miasnikov wrote:
Thanks! LAN & SCSI *.ko related Hyper-V work as need
Please: backport to Slackware 14.0 patches 1b) db63a4c8115a libata 1) cd006086fa5d ata_piix
. . . ( skipped by VVM: as possible non-public msg.)
Pat
--
)
B.H.> as Debian and Ubuntu have done with 3.2-based kernels.
Yes: backport source code related Hyper-V -- is right solution
B.H.> But that sort of large backport isn't allowed on kernel.org stable branches.
I know -- see later "June 04, 2012 3:33 PM"
B.H.> I'm not going to read through all of what you wrote . . . ( skipped by VVM)
No problem, read this:
-- June 08, 2012
-- v3.2.X
-- cd006086fa5d
-- db63a4c8115a
--- URL near phrase "way to cleanly identify Hyper-V but not Virtual PC 7"
{{{
need backport requested at 2012-06-08(!) :
. . .
( look on sub-string "3.2")
http://www.mail-archive.com/linux-kernel@xxxxxxxxxxxxxxx/msg439101.html
Or
==
----- Original Message -----
From: "Victor Miasnikov"
To: "Greg KH" ; "Jonathan Nieder" ; "Andy Whitcroft"
Cc: <stable@xxxxxxxxxxxxxxx>; <linux-kernel@xxxxxxxxxxxxxxx>; "KY Srinivasan"; "Mike Sterling"
Sent: Friday, June 08, 2012 1:36 PM
Subject: Re: Re: ToDo: backport to v3.4 , v3.3 , v3.2 patches 1b) db63a4c8115a libata 1) cd006086fa5d ata_piix: defer
disks to the Hyper-V drivers by default Fw: use hv_storvsc instead of ata_piix for IDE disks ( but not for the CD-ROM)
. . .
{
> > Hyper-V admins need _worked_ Linux v3.4.X / v3.3.X / v3.2.X
> > Please, _fix_ errors related "use hv_storvsc instead of ata_piix to
> > handle the IDE disks devices ( but not for the CD-ROM)"
i.e. need backport to all actual version after 3.1
cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default
and its prerequisite
db63a4c8115a libata: add a host flag to ignore detected ATA devices
}
==
}}}
{{{
Still, if there is a way to cleanly identify Hyper-V but not Virtual PC 7, this would be great!
FIXed: ef773e1..bec35f4
Write in
https://bugzilla.kernel.org/show_bug.cgi?id=52821
}}}
}}}}
B.H.> In short, you need to identify the commit hash for each of the changes you want,
B.H.> and provide the backported patch for any commits
B.H.> that can't simply be cherry-picked.
IMHO:
VVM> In short, MS_HV_Team need to identify the commit hash for each of the changes MS_HV_Team want,
VVM> and provide the backported patch for any commits
VVM> that can't simply be cherry-picked.
B.H.> Please read Documentation/stable_kernel_rules.txt.
Already . . .
Ben, please remember:
==
----- Original Message -----
From: "Victor Miasnikov" vvm
To:
Cc: <stable (at) vger.kernel.org>; . . .
Sent: Monday, June 04, 2012 3:33 PM
Subject: Re: Linux on Hyper-V 1) cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default 2) db63a4c8115a
libata: add a host flag to ignore detected ATA device FW: use hv_storvsc instead of ata_piix to handle the IDE disks
devices ( but not for the ...
Hi!
VVM > > > Hyper-V admins need _worked_ Linux v3.4.X / v3.3.X / v3.2.X
VVM > > >
VVM > > > Please, _fix_ errors related "use hv_storvsc instead of ata_piix to
VVM > > > handle the IDE disks devices ( but not for the CD-ROM)"
. . .
Lots of things would be "nice",
but as this doesn't meet the stable_kernel_rules.txt rules, sorry, I can't take them.
IMHO, patches "does meet the stable_kernel_rules.txt rules" by _all_ criterias . . .
See info correlated with rules:
==
Rules on what kind of patches are accepted, and which ones are not, into the
"-stable" tree:
{
- It must be obviously correct and tested.
Tested ( but, in early implementaition): Ubuntu 12.04 + OpenSUSE
}
{
- It cannot be bigger than 100 lines, with context.
79 lines
+
47 lines
}
. . .
==
Best regards, Victor Miasnikov
Blog: http://vvm.blog.tut.by/
----- Original Message -----
From: "Ben Hutchings"
To: "Victor Miasnikov"
Cc: . . .
Sent: Tuesday, May 28, 2013 6:10 AM
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
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
