linux-kernel - [PATCH 2.6.27] Intel-IOMMU: Typo Fix and correct word in the Comment

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>] [day] [month] [year] [list]

Date:	Tue, 14 Oct 2008 21:07:56 +1100
From:	"Ameya Palande" <2ameya@...il.com>
To:	"Ashok Raj" <ashok.raj@...el.com>,
	"Shaohua Li" <shaohua.li@...el.com>,
	"Anil S Keshavamurthy" <anil.s.keshavamurthy@...el.com>
Cc:	trivial@...nel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 2.6.27] Intel-IOMMU: Typo Fix and correct word in the Comment

Fix for a typo and and replacing incorrect word in the comment.

Signed-off-by: Ameya Palande <2ameya@...il.com>
---

--- drivers/pci/intel-iommu.c.orig      2008-10-14 20:16:59.000000000 +1100
+++ drivers/pci/intel-iommu.c   2008-10-14 20:17:59.000000000 +1100
@@ -587,7 +587,7 @@ static int __iommu_flush_context(struct

        spin_unlock_irqrestore(&iommu->register_lock, flag);

-       /* flush context entry will implictly flush write buffer */
+       /* flush context entry will implicitly flush write buffer */
        return 0;
 }

@@ -680,7 +680,7 @@ static int __iommu_flush_iotlb(struct in
        if (DMA_TLB_IAIG(val) != DMA_TLB_IIRG(type))
                pr_debug("IOMMU: tlb flush request %Lx, actual %Lx\n",
                        DMA_TLB_IIRG(type), DMA_TLB_IAIG(val));
-       /* flush context entry will implictly flush write buffer */
+       /* flush iotlb entry will implicitly flush write buffer */
        return 0;
 }
--
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/