Bug#661318: Possibility integrating newer Hyper-V paravirt drivers in squeeze?
G'day
Am 02.04.2012 02:36, schrieb Jonathan Nieder:
> I suppose my answer was less helpful than it could have been. :)
Thanks Jonathan for enlightening me, now I was able to understand :)
> [...]
>
> The baseline for the current sid kernel is gregkh's 3.2.y kernel.
> When patches meet the criteria described in Documentation/stable_kernel_rules.txt,
Ok, they don't apply to these rules, otherwise they would have been
applied upstream in Greg's tree.
> [...]
> For miscellaneous fixes not in the -stable tree, all that is needed is
> a list of commit ids corresponding to patches' appearance in linus's
> "master" or some tree that feeds into it. Driver backports are also
> often treated this way, and it's probably the right thing to do for
> your case.
I'd say this criteria is matching.
> [...]
>
> Upshot: if you send a list of relevant commit ids for commits that
> are not in 3.2.y, that's a good start, and we can try applying them
> and go from there. (If it's just the list output by
>
> git log --no-merges --oneline v3.2..origin/master \
> -- drivers/hv drivers/staging/hv
>
> then the kernel team could just use that, but I think you mentioned
> needing a few more.)
Yeah a few more, but a helpful command to get started!
> Thanks much and sorry for the lack of clarity.
I keep learning, thank you!
Here it goes: To get a working set of Hyper-V drivers and utils to,
present in 3.4 we need to observe:
drivers/staging/hv
drivers/hv
drivers/scsi/storvsc*
drivers/net/hyperv
drivers/hid/hid-hyperv*
tools/hv/
include/linux/hyperv.h
The merge window is now closed by time of writing this message.
In a follow-up I'll send a list of commit ids - and the order to get
them applied in a way we don't run into merge conflicts :-)
- Mathieu
Reply to: