On Tue, Jun 2, 2015 at 9:53 AM, Shannon Zhao <shannon.zhao@xxxxxxxxxx> wrote:
>
>
> On 2015/6/2 14:37, Greg KH wrote:
>> On Mon, May 18, 2015 at 09:02:36AM +0800, Shannon Zhao wrote:
>>> >
>>> >
>>> > On 2015/5/16 7:09, Greg KH wrote:
>>>> > > On Thu, May 14, 2015 at 09:58:26AM +0800, Shannon Zhao wrote:
>>>>>> > >> > Hi Greg,
>>>>>> > >> >
>>>>>> > >> > Below are the git commit ids of KVM/ARM fixes that should be applied to
>>>>>> > >> > the 3.14-stable kernel tree from top to buttom order.
>>>>>> > >> >
>>>>>> > >> > 2d58b73 arm64: KVM: force cache clean on page fault when caches are off
>>>>>> > >> > 2072d29 arm64: KVM: allows discrimination of AArch32 sysreg access
>>>>>> > >> > 4d44923 arm64: KVM: trap VM system registers until MMU and caches are ON
>>>>>> > >> > a3c8bd3 ARM: KVM: introduce kvm_p*d_addr_end
>>>>>> > >> > 9d218a1 arm64: KVM: flush VM pages before letting the guest enable caches
>>>>>> > >> > 1597930 ARM: KVM: force cache clean on page fault when caches are off
>>>>>> > >> > 46c214d ARM: KVM: fix handling of trapped 64bit coprocessor accesses
>>>>>> > >> > 547f781 ARM: KVM: fix ordering of 64bit coprocessor accesses
>>>>>> > >> > ac30a11 ARM: KVM: introduce per-vcpu HYP Configuration Register
>>>>>> > >> > af20814 ARM: KVM: add world-switch for AMAIR{0,1}
>>>>>> > >> > 8034699 ARM: KVM: trap VM system registers until MMU and caches are ON
>>>>>> > >> > f2ae85b KVM: arm/arm64: vgic: fix GICD_ICFGR register accesses
>>>>>> > >> > 30c2117 KVM: ARM: vgic: Fix the overlap check action about setting the GICD & GICC base address.
>>>>>> > >> > ee9e101 arm64: kvm: use inner-shareable barriers for inner-shareable maintenance
>>>>>> > >> > 63afbe7 kvm: arm64: vgic: fix hyp panic with 64k pages on juno platform
>>>>>> > >> > 4f853a7 arm/arm64: KVM: Fix and refactor unmap_range
>>>> > > I've stopped applying things at this point in time, as this commit, as
>>>> > > you mention, doesn't apply cleanly.
>>>> > >
>>>> > > Can you provide a working backport of it?
>>>> > >
>>>> > > Or better yet, a backport of the ones that you know I will need?
>>>> > >
>>> >
>>> > Of course I can and I have already do that for you. You can get all of
>>> > them from following address:
>>> >
>>> > http://thread.gmane.org/gmane.linux.kernel.stable/134174
>>> >
>>> > And also can get them from:
>>> >
>>> > https://git.linaro.org/people/shannon.zhao/linux-stable.git linux-3.14.y
>> But I just need the ones that need to be backported, not all of them.
>>
> Remove the part you've applied, the rest are the ones that need to be
> backported.
>
>> And I can't dig through web links, nor can I take git pull request, for
>> stable patches.
>
> It makes me confused. I send all the backported patches to you through mail.
>
> Ok, let's make it clearly. Which way do you want me to send you the rest
> patches? Only send the needed ones through mail?
>
Hi Shannon,
I think I understand what Greg would like:
Send an e-mail like a cover letter to a patch series, listing the
upstream commits to be applied (all of them), and then each patch in
an e-mail, with clear comments in each patch which has been modified
(backported) from its original commit with an explanation of why
changes were necessary.
Makes sense?
Thanks,
-Christoffer
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html