[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150519011322.GA7065@dhcp-128-76.nay.redhat.com>
Date: Tue, 19 May 2015 09:13:22 +0800
From: Dave Young <dyoung@...hat.com>
To: "Li, ZhenHua" <zhen-hual@...com>
Cc: joro@...tes.org, linux-pci@...r.kernel.org,
kexec@...ts.infradead.org, bhelgaas@...gle.com,
dwmw2@...radead.org, indou.takao@...fujitsu.com, bhe@...hat.com,
vgoyal@...hat.com, iommu@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, alex.williamson@...hat.com,
ddutile@...hat.com, ishii.hironobu@...fujitsu.com,
doug.hatch@...com, jerry.hoemann@...com, tom.vaden@...com,
li.zhang6@...com, lisa.mitchell@...com, billsumnerlinux@...il.com,
rwright@...com
Subject: Re: [PATCH v11 0/10] iommu/vt-d: Fix intel vt-d faults in kdump
kernel
Hi,
On 05/18/15 at 06:05pm, Li, ZhenHua wrote:
> Hi Joerg,
>
> Testing from HP: passed.
> Testing from He Baoquan(Redhat): passed
>
> The problem that dmar fault came again when running v10 with latest
> kernel is fixed.
> And I think there is no need to update the code to a new version now.
>
> So please tell me if there are still any code need to be changed.
Have you reviewed all my comments? Although it is only iommu driver fixes,
The patches are sent to lkml, no? If you do not want other people's comments
why will you send to us? I would say do not assume it is a closed circle for
only iommu driver.
It is not easy to review patches actually, frankly I feel kernel code review
is not so strict like the early days, maybe one reason is people are getting
tired to argue.
Thanks
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists