linux-kernel - Re: [RFC patch] clean up swiotlb check in intel_iommu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3877989d0908130151l58a73c8cy77791e8e466280bf@mail.gmail.com>
Date:	Thu, 13 Aug 2009 16:51:25 +0800
From:	Luming Yu <luming.yu@...il.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	"Yu, Fenghua" <fenghua.yu@...el.com>,
	"Luck, Tony" <tony.luck@...el.com>,
	LKML <linux-kernel@...r.kernel.org>,
	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC patch] clean up swiotlb check in intel_iommu_init

On Thu, Aug 13, 2009 at 4:23 PM, David Woodhouse<dwmw2@...radead.org> wrote:
> On Thu, 2009-08-13 at 11:11 +0800, Luming Yu wrote:
>>
>> Since swiotlb is an fall back option that might have
>> initialized. We don't need to stop intel_iommu_init
>> because of swiotlb..
>>
>> Please review. If make sense, please apply.
>
> It doesn't apply to the iommu-2.6.git tree.

The patch is against 31-rc5.

If you were not using the attached patch, then I need to use another
mail client to re-send the patch to you. But it is not as convenient
as web gmail
that I'm current using...

If I must generate patch against iommu-2.6.git tree, please point out
the url of that tree,
I can refresh this patch later.

Please let me know what I should do to push this patch in..
--
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/