linux-kernel - Re: [PATCH] intel_irq_remapping: fix a comment error

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]

Date:	Wed, 03 Jun 2015 16:25:22 +0800
From:	Jiang Liu <jiang.liu@...ux.intel.com>
To:	"xiaofeng.yan" <yanxiaofeng@...pur.com>, joro@...tes.org,
	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] intel_irq_remapping: fix a comment error

On 2015/6/3 16:20, xiaofeng.yan wrote:
> change tabke to take.
> 
> Signed-off-by: xiaofeng.yan <yanxiaofeng@...pur.com>
> ---
>  drivers/iommu/intel_irq_remapping.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/iommu/intel_irq_remapping.c b/drivers/iommu/intel_irq_remapping.c
> index 5709ae9..d59f82d 100644
> --- a/drivers/iommu/intel_irq_remapping.c
> +++ b/drivers/iommu/intel_irq_remapping.c
> @@ -46,7 +46,7 @@ static struct hpet_scope ir_hpet[MAX_HPET_TBS];
>   *	->iommu->register_lock
>   * Note:
>   * intel_irq_remap_ops.{supported,prepare,enable,disable,reenable} are called
> - * in single-threaded environment with interrupt disabled, so no need to tabke
> + * in single-threaded environment with interrupt disabled, so no need to take
>   * the dmar_global_lock.
>   */
>  static DEFINE_RAW_SPINLOCK(irq_2_ir_lock);
> @@ -185,6 +185,7 @@ static int modify_irte(int irq, struct irte *irte_modified)
>  		return -1;
>  
>  	raw_spin_lock_irqsave(&irq_2_ir_lock, flags);
> +	while(1):
Hi Xiaofeng,
	Seems above change be removed.
Thanks!
Gerry

>  
>  	iommu = irq_iommu->iommu;
>  
> 
--
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/