Messages in this thread - First message in thread
- "Li, Zhen-Hua"
- "Li, Zhen-Hua"
- "Li, Zhen-Hua"
- "Li, Zhen-Hua"
- "Li, Zhen-Hua"
- "Li, Zhen-Hua"
- "Li, Zhen-Hua"
- "Li, Zhen-Hua"
- "Li, Zhen-Hua"
- "Li, Zhen-Hua"
- "Li, Zhen-Hua"
- Joerg Roedel
- Dave Young
- Dave Young
| | | Date | Fri, 03 Apr 2015 15:54:07 +0800 | From | "Li, ZhenHua" <> | Subject | Re: [PATCH v9 0/10] iommu/vt-d: Fix intel vt-d faults in kdump kernel |
| |
Hi Joerg, This is quite strange. I checked the patches from patch 01 to 10 using ./scripts/checkpatch.pl under the kernel source directory, but got 0 errors and 0 warning. Only some white spaces in the cover letter 00, but is could not be checked by this script.
But I checked the intel-iommu.c using "checkpatch.pl -f", found too many warnings and errors. Maybe we need a new patch to fix them.
Thanks Zhenhua
On 04/02/2015 07:11 PM, Joerg Roedel wrote: > Hi Zhen-Hua, > > On Thu, Mar 19, 2015 at 01:36:18PM +0800, Li, Zhen-Hua wrote: >> This patchset is an update of Bill Sumner's patchset, implements a fix for: >> If a kernel boots with intel_iommu=on on a system that supports intel vt-d, >> when a panic happens, the kdump kernel will boot with these faults: > > I reviewed this patch-set and it is getting closer to a point where it > could be merged. I found a few white-space errors in the review, please > do a check_patch run on the next round and fix these. Besides that and > given some third-party testing and reviews I think we can look forward > to merge it early after the merge-window for v4.1, to give it enough > testing in -next too. > > > Joerg >
| |